Proposed revised format for JDK commit messages

Erik Helin erik.helin at
Tue Sep 18 06:36:02 UTC 2018

On 9/17/18 6:59 PM, Phil Race wrote:
> On 9/17/2018 9:48 AM, Alan Bateman wrote:
>> On 17/09/2018 17:29, Erik Helin wrote:
>>> There are ways we can record the sponshorship, see my reply further 
>>> down. Just for my understanding: this only applies to contributions 
>>> from persons with the "Participant" role [4]? Persons with role 
>>> "Author" [5] still needs a sponsor but we don't record that 
>>> sponsorship, right?
>> It depends on who creates the change-set. Sometimes a contributor with 
>> Author role will create the change-set themselves and the sponsor will 
>> do the push. 
> Can that practice stay the same with git ?

Absolutely, this is a use-case that is very well supported in both hg 
and git.

For hg, the commands are:
- contributor: hg export -r ref > foo.patch
- sponsor: hg import --exact foo.patch

For git, the commands are:
- contributor: git format-patch --stdout ref > foo.patch
- sponsor: git am foo.patch

As you can see, the concept is the same and the commands are fairly 
similar. Both hg and git support a plethora of options when generating 
the patches, see `hg help export` and `git help format-patch` for more 


More information about the skara-dev mailing list