git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: james moger <james.moger@gitblit.com>
Cc: git@vger.kernel.org
Subject: Re: RFE: support change-id generation natively
Date: Mon, 21 Oct 2013 16:51:03 +0200 (CEST)	[thread overview]
Message-ID: <2127507934.9293293.1382367063640.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <1382366880.8925.36578285.27469B22@webmail.messagingengine.com>

for those of us that are not using gerrit...

what is a change-id (semantically, I got from your mail that it is some sort
of unit id set at commit time) and in what way is it different from the 
commit-id ?

Cordialement 

Jérémy Rosen 
+33 (0)1 42 68 28 04

fight key loggers : write some perl using vim 


Open Wide Ingenierie

23, rue Daviel
75012 Paris - France
www.openwide.fr





----- Mail original -----
> Hello Git Community,
> 
> TL;DR:
> It would be a really nice enhancement if the commit command natively
> supported _optionally_ injecting a "Change-Id: I000..." footer in the
> last paragraph of the commit message template and then substituting
> the
> "I000..." value, on commit, with a generated value _without_ having
> to
> rely on a per-repository, native hook or a global hook that affects
> every local repository.
> 
> Full Request:
> Gerrit has established the change-id footer as a prominent and
> wide-spread collaboration identifier.  For those contributing new
> patches to a Gerrit server, it is required to either use EGit/JGit
> (Eclipse) to generate commits [1] OR to use a commit hook script with
> native git to insert a change-id footer during the commit process
> [2].
> This per-repository hook script requirement is an obstacle.  These
> communities would be better served and it would lower the
> contribution
> barrier for many open source projects if native git supported
> change-id
> generation & injection.
> 
> I acknowledge that not everyone uses nor wants to use Gerrit and the
> change-id footer.  That is fine, but it would be a _tremendous_
> usability improvement for those contributing to open source projects
> (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, my C skills are lacking as I live mostly in 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/jgit/api/CommitCommand.java?h=stable-3.1#n288
> [2]
> http://gerrit-documentation.googlecode.com/svn/Documentation/2.0/cmd-hook-commit-msg.html
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2013-10-21 15:05 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 [this message]
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
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=2127507934.9293293.1382367063640.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --cc=git@vger.kernel.org \
    --cc=james.moger@gitblit.com \
    /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).