git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Santi Béjar" <sbejar@gmail.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: Thu, 1 May 2008 18:28:01 -0400	[thread overview]
Message-ID: <20080501222801.GA21731@sigill.intra.peff.net> (raw)
In-Reply-To: <7vd4o5zw2s.fsf@gitster.siamese.dyndns.org>

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, because that is basically
the same point I have been trying to make in this thread.  Santi's
original algorithm for warning about the wrong committer ident was to
check whether it matched the parent commit. But my point was that is a
bad algorithm, because it has way too many false positives (i.e., you
will end up showing the committer _all the time_ in many workflows).
So the followup was "check this other thing, and also look at whether it
matches the parent" to which my response was "why bother checking the
parent match then?"

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.

> I think the other patch about showing the author when you are committing
> other's changes is a good move, by the way.

I agree; it has a very straightforward and sensible algorithm for when
to show.

-Peff

  reply	other threads:[~2008-05-01 22:28 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 [this message]
2008-05-02  9:25                   ` Santi Béjar
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=20080501222801.GA21731@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=raa.lkml@gmail.com \
    --cc=sbejar@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).