From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC - PatchTrack Specification (revised)
Date: Sun, 29 Jul 2012 13:49:05 +1000 [thread overview]
Message-ID: <5014B2B1.9010200@gmail.com> (raw)
In-Reply-To: <201207290515.08289.marek.vasut@gmail.com>
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
next prev parent reply other threads:[~2012-07-29 3:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 13:48 [U-Boot] RFC - PatchTrack Specification (revised) Graeme Russ
2012-07-24 18:41 ` Wolfgang Denk
2012-07-24 22:33 ` Graeme Russ
2012-07-25 10:36 ` Andy Pont
2012-07-25 11:00 ` Wolfgang Denk
2012-07-25 12:50 ` Graeme Russ
2012-07-29 3:15 ` Marek Vasut
2012-07-29 3:49 ` Graeme Russ [this message]
2012-09-22 14:44 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5014B2B1.9010200@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox