> That said, I don't think that --change-id option that the user must not
> forget to use is any better than a hook that the user must not forget to
> install.
Having a --change-id option, to my mind, simplifies use of the patch
workflow as it does not require downloading, copying and setting
exec
On Mon, Oct 21, 2013, at 02:29 PM, Thomas Koch wrote:
> As I understand, a UUID could also be used for the same purbose as the
> change-
> id. How is the change-id generated by the way? Would it be a good english
> name
> to call it enduring commit identifier?
Here is the algorithm:
https://git.
ects
> > (myself included) if something like a "--change-id" flag was
> > implemented and maybe even a config setting to always generate a
> > change-id on commit (EGit currently supports this as
> > "gerrit.createchangeid=true").
> >
> > Sadly, m
n the world of managed
code, but I'd be very happy to cheer for a change-id champion; I suspect
there are some out there who might rally to this cause.
Thanks for your consideration.
James Moger
gitblit.com
[1]
https://git.eclipse.org/c/jgit/jgit.git/tree/org.eclipse.jgit/src/org/eclipse
4 matches
Mail list logo
