From: Thomas Rast <trast@student.ethz.ch>
To: Stephen Kelly <steveire@gmail.com>
Cc: <git@vger.kernel.org>, Ramkumar Ramachandra <artagnon@gmail.com>,
Erik Faye-Lund <kusmabite@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v2] Introduce new configuation option to override committer information
Date: Thu, 20 Jan 2011 13:52:01 +0100 [thread overview]
Message-ID: <201101201352.01874.trast@student.ethz.ch> (raw)
In-Reply-To: <ih95il$62b$2@dough.gmane.org>
Stephen Kelly wrote:
>
> Is this patch going to become part of git, or is it in already?
>
> If not it will probably just get lost because there is no issue tracker.
Discussion stalled without an agreement that any patch proposed is
"good", so if it ends here it will be dropped.
You could probably help getting closer to a solution by:
* Not dropping Cc's all the time. I saw this email just by chance.
* Stating *why* this cannot be solved in any other way on the KDE
end. So far you only said
> > Is it impossible to fix this on the KDE side? I would think a
> > many-to-one mapping from committer identities to bugzilla account
> > names could be a useful thing to have in any case.
>
> I asked that before coming here, and apparently that is not possible.
My gut feeling is that a footer line in the commit along the lines
of
Bugzilla-Id: Registered Name <registered.email@example.com>
would work. I suspect others have a similar feeling. A good case
why this is not a feasible solution for (presumably) border cases
like you would help get rid of it.
* Replying to e.g.
http://mid.gmane.org/201101111542.15185.trast@student.ethz.ch
with (ideally better) ideas of what the semantics should be. My
assessment is that it either conflicts with user expectations or
with established git-config mechanisms of how the various files
override each other.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2011-01-20 12:52 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
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 [this message]
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=201101201352.01874.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=kusmabite@gmail.com \
--cc=steveire@gmail.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).