From: Stephen Kelly <steveire@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Introduce new configuation option to override committer information
Date: Sat, 08 Jan 2011 20:24:01 +0100 [thread overview]
Message-ID: <igadki$4tb$2@dough.gmane.org> (raw)
In-Reply-To: 1294473809-11850-1-git-send-email-artagnon@gmail.com
Ramkumar Ramachandra wrote:
> Currently, there is no way to set committer information on a
> per-repository basis. The 'user.name' and 'user.email' configuration
> options set both author and committer information. To solve this,
> introduce 'user.committername' and 'user.committeremail' configuration
> options to override committer name and email respectively.
>
> Reported-by: Stephen Kelly <steveire@gmail.com>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.co
<snip>
Thanks for working on this. I wanted to try it out, but it no longer applies
cleanly since 4c28e4ada03f5440251545cf91e0d81bce9b010d and after trivial
merging, I can't build.
Can you update the patch?
Thanks,
Steve.
next prev parent reply other threads:[~2011-01-08 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 13:16 Wish: make commiter email address configurable per-repo Stephen Kelly
2011-01-07 13:20 ` Thomas Rast
2011-01-07 13:23 ` Stephen Kelly
2011-01-07 13:43 ` Thomas Rast
2011-01-07 18:01 ` Stephen Kelly
2011-01-07 18:19 ` Erik Faye-Lund
2011-01-20 18:44 ` Junio C Hamano
2011-01-08 8:03 ` [PATCH] Introduce new configuation option to override committer information Ramkumar Ramachandra
2011-01-08 19:24 ` Stephen Kelly [this message]
2011-01-09 10:29 ` [PATCH v2] " Ramkumar Ramachandra
2011-01-09 17:24 ` Jonathan Nieder
2011-01-11 13:41 ` Stephen Kelly
2011-01-11 14:19 ` Ramkumar Ramachandra
2011-01-11 14:42 ` Thomas Rast
2011-01-20 19:00 ` Junio C Hamano
2011-01-20 11:16 ` Stephen Kelly
2011-01-20 12:52 ` Thomas Rast
2011-01-20 15:24 ` Stephen Kelly
2011-01-20 19:19 ` Jonathan Nieder
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='igadki$4tb$2@dough.gmane.org' \
--to=steveire@gmail.com \
--cc=git@vger.kernel.org \
/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).