From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sat, 09 Jul 2011 08:01:07 +0200 Subject: [U-Boot] [PATCH v1 (WIP) 00/16] [Timer]API Rewrite In-Reply-To: <4E164E5C.6010406@gmail.com> References: <1309261269-4363-1-git-send-email-graeme.russ@gmail.com> <4E164E5C.6010406@gmail.com> Message-ID: <4E17EEA3.6000903@aribaud.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Greame, Le 08/07/2011 02:25, Graeme Russ a ?crit : > 1) I understand that you would like each individual patch in the series to > have the in-reply-to header set to the individual parent patch and not have > the whole series in-reply-to the first (00/16) patch? (It will be a bit of > a PITA to set in-reply-to for 16 individual patches, but I will do if that > is the way you want it) Not sure what you mean here, but if it is "make patch i/N of a series have be a reply-to patch i/N of the previous series, I agree that it would be a PITA which is not worth the effort considerong the benefit. (the only benefit I can see is to be able to find back the previous series and e.g. check that comments to patch i/N-1 were taken into account by patch i/N. This can be accomplished more easily by having series N-1 and N in a local branch and doing a git diff between commits i/N and i/N-1) Amicalement, -- Albert.