[U-Boot] RFC - PatchTrack Specification (revised)
Graeme Russ
graeme.russ at gmail.com
Sun Jul 29 05:49:05 CEST 2012
Hi Marek,
For future reference, please comment against:
Take a look at http://www.denx.de/wiki/U-Boot/ToolsPatchTracking
On 07/29/2012 01:15 PM, Marek Vasut wrote:
> Dear Graeme Russ,
>
> You might want to actually create an mbox of all these stacked patches so people
> can download and apply them and rebase their patches on top of them.
Under 'Web Interface':
"Download a patch set of all patches meeting a specific criteria (pass all
stand-alone and inter-dependent tests and have been acked for example)"
This could be an mbox file or an archive (.tgz) of patches
>> Operation Sequence - Revised version of existing patch
[snip]
>
> Yes? Maybe this should be applied at the place where the old patch was, rather
> than on top.
Revised version of existing patch
- Remove existing patch from patch stack
- Insert new patch into patch stack at same location as the removed patch
- Run each configured static test against the patch
- Run each configured dynamic test against the patch
- Record the results of the static and dynamic tests against the patch
So yes, in place of the existing patch
> Why not make committed like ... lavender or something </jab> ? :)
:P
>
> [...]
> The rest sounds quite cool.
Good :)
Regards,
Graeme
More information about the U-Boot
mailing list