From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t0091: allow test in a repository without tags
Date: Tue, 06 Feb 2024 10:33:29 -0800 [thread overview]
Message-ID: <xmqqeddpigsm.fsf@gitster.g> (raw)
In-Reply-To: <CAN0heSrX8zQnfk_abtgBreoc=a8Z+7E-jEHHUFmu6740L8p2Lw@mail.gmail.com> ("Martin Ågren"'s message of "Mon, 5 Feb 2024 11:07:16 +0100")
Martin Ågren <martin.agren@gmail.com> writes:
> GIT-VERSION-GEN seems to be careful to only use tags on the wanted form.
> My build generates a git version of "2.43.GIT", no "unknown..." stuff.
>
> I don't doubt that you've hit this, I just wonder which piece of the
> puzzle I'm missing.
I wonder that too.
I was experimenting with "seen" with the reftable. I first created
a new and empty repository with "git init --ref-format=reftable" in
a brand new directory next to my primary working area, and then did
"git fetch --no-tags ../git.git/ master" or something to pull the
history without tags in. After that I thought I was careful to make
sure I only ran the "seen" version of Git (all my other installations
of Git are unaware of reftable, and the version of Git on my regular
$PATH is not from the "seen" branch), but perhaps I screwed up at
some point and the mistake got stuck in the version file, or something
silly like that, perhaps.
>
>> - # The beginning should match "git version --build-info" verbatim,
>> + # The beginning should match "git version --build-options" verbatim,
>
> Correct, my thinko-typo, thanks for correcting.
>
>> # but rather than checking bit-for-bit equality, just test some basics.
>> - grep "git version [0-9]." system &&
>> + grep "git version " system &&
>
> This matches the commit message, ok.
>
> Martin
prev parent reply other threads:[~2024-02-06 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 19:03 [PATCH] t0091: allow test in a repository without tags Junio C Hamano
2024-01-30 20:53 ` Eric Sunshine
2024-01-30 21:46 ` Junio C Hamano
2024-02-05 10:07 ` Martin Ågren
2024-02-06 18:33 ` 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=xmqqeddpigsm.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@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).