From: Stefan Beller <sbeller@google.com>
To: Orgad Shaneh <orgads@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] name-rev: Fix tag lookup on repository with mixed types of tags
Date: Thu, 22 Jun 2017 13:38:30 -0700 [thread overview]
Message-ID: <CAGZ79kYFcZ_wMQ5grH-keFpnf=V7Y=3KkAJEH3AuoZYMDvqTTQ@mail.gmail.com> (raw)
In-Reply-To: <20170622195245.11252-1-orgads@gmail.com>
On Thu, Jun 22, 2017 at 12:52 PM, <orgads@gmail.com> wrote:
> From: Orgad Shaneh <orgads@gmail.com>
>
> Commit 7550424804 (name-rev: include taggerdate in considering the best
> name) introduced a bug in name-rev.
>
> If a repository has both annotated and non-annotated tags, annotated
> tag will always win, even if it was created decades after the commit.
>
> Consider a repository that always used non-annotated tags, and at some
> point started using annotated tags - name-rev --tags will return the
> first annotated tags for all the old commits (in our repository it is
> followed by ~5067 for one commit, or by ~120^2~21^2~88^2~87 for
> another...). This is obviously not what the user expects.
>
> The taggerdate should only be matched if *both tags* have it.
Please sign off the patch. See https://developercertificate.org/
or Documentation/SubmittingPatches
> ---
> builtin/name-rev.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/name-rev.c b/builtin/name-rev.c
> index 92a5d8a5d2..8f77023482 100644
> --- a/builtin/name-rev.c
> +++ b/builtin/name-rev.c
> @@ -46,11 +46,13 @@ static void name_rev(struct commit *commit,
> commit->util = name;
> goto copy_data;
> } else if (name->taggerdate > taggerdate ||
> - (name->taggerdate == taggerdate &&
> + ((taggerdate == ULONG_MAX || name->taggerdate == taggerdate) &&
> name->distance > distance)) {
> copy_data:
> name->tip_name = tip_name;
> - name->taggerdate = taggerdate;
> + if (taggerdate != ULONG_MAX) {
> + name->taggerdate = taggerdate;
> + }
style: you may omit the braces for a single statement
after if.
> name->generation = generation;
> name->distance = distance;
> } else
> --
> 2.13.1.windows.1.1.ga36e14b3aa
>
next prev parent reply other threads:[~2017-06-22 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 19:52 [PATCH] name-rev: Fix tag lookup on repository with mixed types of tags orgads
2017-06-22 20:38 ` Stefan Beller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-18 13:24 orgads
2017-10-19 1:54 ` Junio C Hamano
2017-06-22 19:42 Orgad Shaneh
2017-06-22 22:03 ` Junio C Hamano
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='CAGZ79kYFcZ_wMQ5grH-keFpnf=V7Y=3KkAJEH3AuoZYMDvqTTQ@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=orgads@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).