git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Oliver Blanthorn <freedom4cows@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: Bug report: ":/[text]" revision reference no longer returns youngest commit
Date: Sun, 15 Dec 2024 09:43:23 -0800	[thread overview]
Message-ID: <xmqqzfkw970k.fsf@gitster.g> (raw)
In-Reply-To: <CADFnu5sMEvGyGy7xH1r0NGBUZJBznCi0waJ_bJ3tSHQ5Y2yX1Q@mail.gmail.com> (Oliver Blanthorn's message of "Sun, 15 Dec 2024 12:51:40 +0100")

Oliver Blanthorn <freedom4cows@gmail.com> writes:

> What did you do before the bug happened? (Steps to reproduce your issue)
>
> `git show :/Merge` in git's git repo
>
>
>
> What did you expect to happen? (Expected behavior)
>
> The most recent commit matching the text "Merge" should have appeared
>
>
>
> What happened instead? (Actual behavior)
>
> A commit from 19 years ago appeared

Thanks for a well written report.  I think this is the same breakage
reported in *1*, which was fixed with *2*.  Hopefully the fix will
be part of the upcoming Git 2.48, scheduled soon after the new year.


[References]

 *1* https://lore.kernel.org/git/CAKOEJdcPYn3O01p29rVa+xv=Qr504FQyKJeSB-Moze04ViCGGg@mail.gmail.com/

 *2* https://lore.kernel.org/git/20241206-pks-rev-parse-fix-reversed-list-v3-1-d934c17db168@pks.im


      parent reply	other threads:[~2024-12-15 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 11:51 Bug report: ":/[text]" revision reference no longer returns youngest commit Oliver Blanthorn
2024-12-15 12:25 ` Kristoffer Haugsbakk
2024-12-15 20:50   ` Junio C Hamano
2024-12-15 17:43 ` Junio C Hamano [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=xmqqzfkw970k.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=freedom4cows@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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).