| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
|
|
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
|
|
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
|
|
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
|
|
First real data to play with \o/
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
|
|
Use a regex rule to match patchwork instances within the schema. The
validator/title parser shall use the key as part of the URL to obtain
further patch information.
Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
|
|
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>
|
|
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>
|
