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. > 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: sta...@xenproject.org [4.2+] > or > CC: sta...@xenproject.org # 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: sta...@xenproject.org (4.2+) Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
