From: Stephen Kelly <steveire@gmail.com>
To: git@vger.kernel.org
Subject: Re: Wish: make commiter email address configurable per-repo
Date: Fri, 07 Jan 2011 19:01:54 +0100 [thread overview]
Message-ID: <ig7kej$j4p$1@dough.gmane.org> (raw)
In-Reply-To: 201101071443.51574.trast@student.ethz.ch
Thomas Rast wrote:
> Stephen Kelly wrote:
>> Thomas Rast wrote:
>> > See user.email in git-config(1). Most people set it globally, as in
>> >
>> > git config --global user.email "author@example.com"
>> >
>> > but there's nothing stopping you from doing
>> >
>> > git config user.email "alias@example.com"
>> >
>> > to set it on a per-repo level. (Or just edit .git/config, of course.)
>>
>> Doesn't this set both the author and the committer?
>
> Oh, I see. Yes, it does.
>
> Stephen Kelly wrote earlier:
>> If my email address that I use for committing is not the same as that
>> configured in the bugzilla, the automated bug closing does not work.
>
>
> Probably if KDE has this use-case then that means we need to implement
> it as a feature on size alone, but I briefly looked into the code and
> it requires a bit more restructuring than I'm willing to do over
> coffee.
>
> I think as a stop-gap measure you'll have to use an alias such as
>
> ci = commit --author="your usual <author>"
>
> along with a local setting for user.email to force them to be
> different. (Note that this will re-set the author when saying 'git
> ci --amend' on other people's commits!)
>
Thanks for looking into it!
I'll consider the alias you suggest. Git command aliases can be configured
per repo, right?
Is there a bug tracker used for git so that this issue doesn't get lost?
All the best,
Steve.
next prev parent reply other threads:[~2011-01-07 18:02 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 [this message]
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
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='ig7kej$j4p$1@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).