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

["Bird, Timothy" <Tim.Bird@am.sony.com>]

> -----Original Message-----
> From: ksummit-discuss-bounces@lists.linuxfoundation.org [mailto:ksummit-
> discuss-bounces@lists.linuxfoundation.org] On Behalf Of Christoph Lameter
> Sent: Friday, July 29, 2016 7:21 AM
> To: David Howells <dhowells@redhat.com>
> Cc: ksummit-discuss@lists.linuxfoundation.org
> Subject: Re: [Ksummit-discuss] [ANNOUNCE] git-series: track changes to a patch
> series over time
> 
> On Fri, 29 Jul 2016, David Howells wrote:
> 
> > Josh Triplett <josh@joshtriplett.org> wrote:
> >
> > > Note that git-series doesn't provide a quilt-style push/pop workflow,
> > > with applied and unapplied patches; it just looks at HEAD.
> >
> > Ah...  In that case it's probably not a sufficient substitute for how I use
> > stgit.
> 
> Did not know that there was stgit. Still stuck on quilt since
> I like editing the files directly (its often easier to edit the diffs if
> you want to rename things etc).
> 
> Interesting projects.

Indeed.  For many years I used a quilt-based workflow.  Recently
I've been trying to convert to a pure git-based workflow, but for
some reason git rebase -I always seems to give me problems.  It
always takes me much longer to just move some hunk from one
commit to another than it did in quilt using the patches and vi.

I don't know if git-series addresses that particular problem, but
Josh mentioned enough other problems that I have every time I
prepare patches for upstream, that I definitely plan to check out
the tool.
 -- Tim