All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: "Git List" <git@vger.kernel.org>,
	"Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: Re: sudo: git describe during GIT_VERSION_GEN not as expected..
Date: Sun, 15 May 2022 09:51:52 -0700	[thread overview]
Message-ID: <xmqqwnem7n87.fsf@gitster.g> (raw)
In-Reply-To: <7bb71920-b840-5133-ceac-664c09942772@iee.email> (Philip Oakley's message of "Sun, 15 May 2022 11:12:29 +0100")

Philip Oakley <philipoakley@iee.email> writes:

> I have run into a problem with make/install of git on my old travel
> laptop. While trying to make / install git with some patches on top of 
> yesterdays next (coincidental timing) I'm finding that the generated
> git version is the default value rather than that of a regular 'get 
> describe' as used in GIT_VERSION_GEN.

Yup, we've been discussing on this issue since the Git 2.35.3 (and
friends) and Git 2.36 release.

  https://lore.kernel.org/git/20220426183105.99779-1-carenas@gmail.com/

I think the last round:

  https://lore.kernel.org/git/20220513010020.55361-1-carenas@gmail.com/

is more or less done, so perhaps we should start merging it down to
'next' and all the way down to the older maintenance tracks like
maint-2.30 that are affected.

Thanks.

      parent reply	other threads:[~2022-05-15 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 10:12 sudo: git describe during GIT_VERSION_GEN not as expected Philip Oakley
2022-05-15 10:38 ` Philip Oakley
2022-05-15 11:05 ` Carlo Arenas
2022-05-15 11:38   ` Philip Oakley
2022-05-15 16:51 ` 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=xmqqwnem7n87.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=philipoakley@iee.email \
    /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.