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

[Josh Triplett <josh@joshtriplett.org>]

On Fri, Jul 29, 2016 at 01:20:12PM +0100, David Howells wrote:
> Josh Triplett <josh@joshtriplett.org> wrote:
> > I'd like to announce a project I've been working on for a while.  I sent
> > this announcement to LKML, but since many people don't subscribe to LKML
> > directly, and since ksummit-discuss has had several discussions
> > specifically about patch workflow and development processes, I thought
> > I'd send the announcement here as well, in case anyone found it useful
> > for their workflow.
> 
> Can this be used as a direct substitute for stgit for maintaining a patch
> series?

Yes, that's exactly what I designed it for.  git-series has the added
advantage of tracking the versions of the patch series across rewrites.
stgit just directly rewrites history, like rebase -i does; as far as I
know, it doesn't remember the old history.  You'd have to go to the
reflog for that.  git-series lets you rewrite history (using rebase -i
or any other tool you like), but actually tracks the history of your
patch series across rewrites, complete with commit messages.

Note that git-series doesn't provide a quilt-style push/pop workflow,
with applied and unapplied patches; it just looks at HEAD.