Re: [Xen-devel] tags in backport commits

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

On Tue, 13 Jun 2017, Ian Jackson wrote:
> Stefano Stabellini writes ("tags in backport commits"):
> > Specifically, I would like to see a tag that specifies the id of the
> > original commit, like "master commit" that Jan is using today. I would
> > prefer if the tag didn't have any spaces, thus, I suggest
> > master-commit-id or upstream-commit-id (that's what I use in the
> > qemu-xen trees because it wouldn't be clear what "master" is in that
> > context). Whatever is chosen should be documented under docs.
> 
> I suggest we allow what "git cherry-pick -x" does.
 
It's a bit wordy but the undeniable convenience of being able to add the
tag with just a "-x" is awesome, so I am all for it! :-)


> > Moreover, I think we should start using tags in our staging commits
> > which specify to which trees a given commit should be backported to as
> > soon as it passes the push gate. I suggest to use something similar to
> > the Linux kernel:
> > 
> >   CC: stable@xxxxxxxxxxxxxx [4.2+]
> > or
> >   CC: stable@xxxxxxxxxxxxxx # 4.2+
> > 
> > But anything else that allows us to specify a range of stable trees
> > would be fine by me. This is the first step toward backport automation.
> > What do you think?
> 
> I have no objection to this.  I suggest ( ) as punctuation, because
> those are comments in email addresses so everything will still work.
> Ie
> 
>    CC: stable@xxxxxxxxxxxxxx (4.2+)

Sure. We need actually a stable@xxxxxxxxxxxxxx mailing list for this to
work so that the stable maintainers can comment on the tags.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel