From: "Santi Béjar" <sbejar@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Alex Riesen" <raa.lkml@gmail.com>
Subject: Re: [PATCH 3/3] commit: Show the committer ident when is different from the parent
Date: Fri, 2 May 2008 11:25:38 +0200 [thread overview]
Message-ID: <8aa486160805020225p47230100m86f9ee251dabc161@mail.gmail.com> (raw)
In-Reply-To: <20080501222801.GA21731@sigill.intra.peff.net>
On Fri, May 2, 2008 at 12:28 AM, Jeff King <peff@peff.net> wrote:
> On Thu, May 01, 2008 at 12:02:51PM -0700, Junio C Hamano wrote:
>
> > Once you have a good algorithm to see when to trigger the warning that the
> > user might be using an unintended committer identity, I do not think you
> > should refrain from issuing the warning when you see the offending
> > committer ident and whose commit you are building on top of should not
> > affect it. Otherwise, the user will get the warning once (or not even get
>
> I think I must not be writing very clearly,
It was clear, but I think there is more than this, especially the
definition of what is a wrong committer depends on the user. I was
trying to not annoy too much to some users (those who like the
automatic committer).
Let's find the definition of "wrong committer":
1) user.{name,email} or GIT_COMMITTER_{NAME,EMAIL} is not a wrong committer.
2) automatic without a domain name (user@hostname.(none)) is a wrong committer.
2) automatic or partially set ident:
a) wrong committer for some users
b) right committer for others
I see different strategies. Show the committer:
1) always
2) when user.warn = yes (defaulting to yes)
3) when it is automatic
a) always
b) and different from parent
c) and different from a list of valid committer idents
d) and when user.WarnAutomatic = yes (defaulting to yes)
(the names of the configs are just ideas)
I prefer in order: 3a, 3d, 2, 1.
>
> I also think you could argue that we should just show the committer all
> the time. But I don't think anyone has made that argument.
>From past threads and the "precious screen state" I thought it was
totally discarded.
Santi
next prev parent reply other threads:[~2008-05-02 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 8:47 [PATCH 0/3] Show author and/or committer in some cases Santi Béjar
2008-04-30 8:47 ` [PATCH 1/3] Preparation to call determine_author_info from prepare_to_commit Santi Béjar
2008-04-30 8:47 ` [PATCH 2/3] commit: Show author if different from committer Santi Béjar
2008-04-30 8:47 ` [PATCH 3/3] commit: Show the committer ident when is different from the parent Santi Béjar
2008-04-30 14:50 ` Jeff King
2008-04-30 15:10 ` Jeff King
2008-04-30 16:37 ` Jeff King
2008-04-30 19:23 ` Santi Béjar
2008-04-30 19:26 ` Jeff King
2008-05-01 8:34 ` Santi Béjar
2008-05-01 13:51 ` Jeff King
2008-05-01 19:02 ` Junio C Hamano
2008-05-01 22:28 ` Jeff King
2008-05-02 9:25 ` Santi Béjar [this message]
2008-04-30 17:52 ` Alex Riesen
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=8aa486160805020225p47230100m86f9ee251dabc161@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=raa.lkml@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).