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

[Josh Triplett <josh@joshtriplett.org>]

On Mon, Aug 15, 2016 at 02:20:04PM +0100, James Hogan wrote:
> On Fri, Aug 05, 2016 at 10:26:15AM -1000, Josh Triplett wrote:
> > On Fri, Aug 05, 2016 at 02:52:18AM +0300, Michael S. Tsirkin wrote:
> > > And how about "git series cherry-pick" - to apply
> > > series to the current head?
> > 
> > Could you elaborate on the semantic of this?  You have a series in your
> > tree, and you want to take all the patches in the series and apply them
> > to HEAD?  Or, do you want to copy the series and rebase the copy on HEAD?
> > 
> > For the former, once I add support for formatting a series other than
> > the current one, you could do that with "git series format seriesname
> > --stdout | git am".
> 
> FWIW I had to do the latter the other day to check which stable branches
> needed distinct backports. Since git series doesn't seem to allow
> "forking" of a series yes (i.e. analagous to git checkout -b b1 b2), i
> ended up doing something along the lines of this repeatedly:
> 
> git branch git-series/$feature/stable/4.7 git-series/$feature/staging
> git series checkout git-series/$feature/stable/4.7
> git series rebase v4.7
> etc
> 
> (so the new series inherits / branches the history of the old one)
> 
> So it'd be nice to be able to do something like this instead:
> git series checkout -b new_series [old_series = current_series]
> git series rebase v4.7

That seems completely reasonable; thanks for the suggestion!