| Age | Commit message (Collapse) | Author |
|---|
|
This may be subject to further change so that we can ensure only one parent
exists, or that keys are unique in the dependencies list for example.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Provide the option to specify a URL or patchwork number reference.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Reduce the specific 'torvalds' and 'linux-next' sequences to mappings of
their own.
This allows the following syntax:
upstream:
- torvalds: 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d # Linux 4.19
- torvalds: 6d9666fb78526a7728cc4954ec1da4c2b416753d
- next: e0868bcfd529997cf98da1dd14bab8cb8175eda7
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Define the acceptable list of assignees, and remove the duplicated field.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Utilise pykwalify to provide a YAML schema for our data files. Define
an initial project schema under projects/ to define our data layout. An
example task data file is provided to demonstrate how the data could be
presented in text form.
A validator is provided which currently simply calls pykwalify. This is
just an initial demonstration of the validation process and can be
expanded upon later to provide automa{t,g}ic commit title processing,
and further business logic can be added with extra tools.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
Data is stored through a folder hierarchy in yaml data files. Data can be
edited by hand and validated using the provided schema files or tools can
be developed to aid the creation and manipulation of the data sources.
|
|
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
|
