From mboxrd@z Thu Jan 1 00:00:00 1970 From: Graeme Russ Date: Sun, 29 Jul 2012 13:49:05 +1000 Subject: [U-Boot] RFC - PatchTrack Specification (revised) In-Reply-To: <201207290515.08289.marek.vasut@gmail.com> References: <201207290515.08289.marek.vasut@gmail.com> Message-ID: <5014B2B1.9010200@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 ? :) :P > > [...] > The rest sounds quite cool. Good :) Regards, Graeme