From: Martin Fick <mfick@codeaurora.org>
To: james.moger@gitblit.com
Cc: Thomas Koch <thomas@koch.ro>,
Jeremy Rosen <jeremy.rosen@openwide.fr>,
git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: RFE: support change-id generation natively
Date: Mon, 21 Oct 2013 12:49:49 -0600 [thread overview]
Message-ID: <201310211249.49568.mfick@codeaurora.org> (raw)
In-Reply-To: <1382380858.25852.36711509.53CF173C@webmail.messagingengine.com>
On Monday, October 21, 2013 12:40:58 pm
james.moger@gitblit.com wrote:
> 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.eclipse.org/c/jgit/jgit.git/tree/org.eclipse.
> jgit/src/org/eclipse/jgit/util/ChangeIdUtil.java#n78
>
> I think "enduring commit id" is a fair interpretation of
> it's purpose. I don't speak for the Gerrit developers so
> I can not say if they are interested in alternative id
> generation. I come to the list as a change-id
> user/consumer.
As a Gerrit maintainer, I would suspect that we would
welcome a way to track "changes" natively in git. Despite
any compatibility issues with the current Gerrit
implementation, I suspect we would be open to new forms if
the git community has a better proposal than the current
Change-Id. Especially if it does reduce the significant
user pain point of installing a hook!
-Martin
--
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-10-21 18:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 14:48 RFE: support change-id generation natively james.moger
2013-10-21 14:51 ` Jeremy Rosen
2013-10-21 15:41 ` james.moger
2013-10-21 16:35 ` Shawn Pearce
2013-10-21 16:38 ` Ondřej Bílka
2013-10-21 23:07 ` Shawn Pearce
2013-10-21 18:29 ` Thomas Koch
2013-10-21 18:40 ` james.moger
2013-10-21 18:49 ` Martin Fick [this message]
2013-10-22 19:50 ` Junio C Hamano
2013-10-22 20:06 ` Pyeron, Jason J CTR (US)
2013-10-22 20:43 ` Junio C Hamano
2013-10-23 6:36 ` Duy Nguyen
2013-10-23 16:00 ` Junio C Hamano
2013-10-24 2:07 ` Duy Nguyen
2013-10-24 4:11 ` Nasser Grainawi
2013-10-24 5:25 ` Duy Nguyen
2013-10-24 6:01 ` Johannes Sixt
2013-10-24 12:11 ` james.moger
2013-10-24 12:51 ` Thomas Koch
2013-10-24 13:31 ` Duy Nguyen
2013-10-24 20:04 ` Junio C Hamano
2013-10-25 6:37 ` Johannes Sixt
2013-10-21 23:10 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201310211249.49568.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
--cc=james.moger@gitblit.com \
--cc=jeremy.rosen@openwide.fr \
--cc=spearce@spearce.org \
--cc=thomas@koch.ro \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).