Re: [ANNOUNCE] git-series: track changes to a patch series over time

From: Richard Ipsum <richard.ipsum@codethink.co.uk>
Date: Jul 31, 2016, 14:09 UTC
Message-ID: <20160731140936.GA3959@salo>
In-Reply-To: <CAGZ79kbTViNYLq0aouQ--5d7m=HYi3QxUYqaaH8sTCS_YTDquQ@mail.gmail.com>

On Fri, Jul 29, 2016 at 09:59:08AM -0700, Stefan Beller wrote:

Show 17 quoted lines

> On Fri, Jul 29, 2016 at 5:44 AM, Richard Ipsum
> <richard.ipsum@codethink.co.uk> wrote:
> >>
> >> These definitely seem like a family of related problems.  I'd like to
> >> use git-series as a format for storing iterations on things like GitHub
> >> pull-requests or Gerrit patch versions (in the latter case, overcoming
> >> Gerrit's limitations on only handling one patch at a time).  Integrating
> >> reviews with that seems helpful.
> >
> > Worth noting here that Gerrit's one patch per change format isn't
> > intrinsic to Notedb, since we just need to track the sha we want
> > to merge and optionally the branch we intend to merge into.
> 
> Note that Gerrit started to lose the "one patch at a time" notion.
> It is possible to at least submit multiple changes coupled together
> (even across project boundaries) via the topic. Some sort of cover
> letter is missing though, that could be used e.g. for the merge commit.

Potentially my misuse of the format but git-candidate puts the cover letter into the body of the commit message before the footers begin, for each new patchset added to the change. This has the advantage that you can track each version of the cover letter, since there's one per patchset.