Preserving changeset authorship (was Re: PING: [PATCH] Enable debug info on all libraries for OpenJDK builds)
mark.reinhold at oracle.com
mark.reinhold at oracle.com
Thu May 9 22:20:11 UTC 2013
2013/5/9 8:14 -0700, philip.race at oracle.com:
>> (Yes, this is one of those rare cases in which a sponsor should use
>> the -u option.)
>
> I'd hazard a guess that there are number of people who overlook this option
> in part because they don't realise you can do
>
> hg commit -u <SOMEBODY-ELSE> ...
>
> I was kind of surprised myself when I first learned to do this as it
> seemed odd that someone else could claim a changeset was from
> another person. I thought you would need their private key to
> be able to do that.
No, your ssh key is used only to authenticate you to the hg server when
you do a push. Modulo the constraints imposed by jcheck, you can use
the -u option to set the username string to anything you want.
FYI, in recent versions of Mercurial the -u option is, conveniently,
supported in commands other than commit, e.g., import, qnew, and qref.
- Mark
More information about the build-dev
mailing list