From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Jeff King" <peff@peff.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Andreas Schwab" <schwab@linux-m68k.org>,
"Olaf Hering" <olaf@aepfle.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH] name-rev: include taggerdate in considering the best name
Date: Sun, 24 Apr 2016 08:35:53 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1604240831470.2896@virtualbox> (raw)
In-Reply-To: <xmqq60v9pduf.fsf@gitster.mtv.corp.google.com>
Hi,
[fixing Uwe's email address, as the address bounces that was recorded in
the commit introducing the flawed behavior, and I failed to check mailmap
earlier.]
On Fri, 22 Apr 2016, Junio C Hamano wrote:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> > ... I think this is still the simplest model we can use
> > without trying to really do a topo-sort. And in many ways it's the
> > simplest one to explain to people too: "we try to use the oldest
> > reference we can find as a base for the resulting name" is not a
> > complex or hard concept to explain.
>
> Yes, the more I look at Dscho's patch, the more like it exactly for
> that reason. Its behaviour is very simple from the end-user's point
> of view, unlike the historical one.
Well, seeing as I introduced the bug, it's only fair that I fix it, too.
Ciao,
Dscho
prev parent reply other threads:[~2016-04-24 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 13:39 [PATCH] name-rev: include taggerdate in considering the best name Johannes Schindelin
2016-04-22 18:11 ` Jeff King
2016-04-22 18:27 ` Junio C Hamano
2016-04-22 18:40 ` Junio C Hamano
2016-04-22 18:45 ` Linus Torvalds
2016-04-22 20:50 ` Junio C Hamano
2016-04-24 6:35 ` Johannes Schindelin [this message]
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=alpine.DEB.2.20.1604240831470.2896@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=olaf@aepfle.de \
--cc=peff@peff.net \
--cc=schwab@linux-m68k.org \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.