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

[Josh Triplett <josh@joshtriplett.org>]

On Fri, Aug 05, 2016 at 02:52:18AM +0300, Michael S. Tsirkin wrote:
> On Fri, Jul 29, 2016 at 12:50:39AM -0700, Josh Triplett wrote:
> > I'd welcome any feedback, whether on the interface and workflow, the
> > internals and collaboration, ideas on presenting diffs of patch series,
> > or anything else.
> 
> Hi Josh!
> A couple of ideas, I hope these will be helpful:
> 
> I often need to move series between unrelated trees.
> I sometimes use cherry-pick for that (if they are from my tree)
> or am (if not).
> 
> How about "git series am" - get patch series from email,
> including a cover letter, and create a series from that?

Would you expect to feed this one mbox containing all the mails, or a
set of files containing one patch each (including the 0000 cover
letter), or both?

> 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".

> Kind of going in the reverse direction from git series format.

I like the idea; I'd like to offer more "import" mechanisms for any
other patch-series format people find useful.

- Josh Triplett