From: Philip Oakley <philipoakley@iee.email>
To: Carlo Arenas <carenas@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: sudo: git describe during GIT_VERSION_GEN not as expected..
Date: Sun, 15 May 2022 12:38:01 +0100 [thread overview]
Message-ID: <7515c5df-a547-c4dc-5221-0f5089f2a2c3@iee.email> (raw)
In-Reply-To: <CAPUEspjGiyUOhEZpe1bZ3EQqAruyT-WoC8xorxNfp=ktOw__uw@mail.gmail.com>
Hi Carlo
On 15/05/2022 12:05, Carlo Arenas wrote:
> On Sun, May 15, 2022 at 3:12 AM Philip Oakley <philipoakley@iee.email> wrote:
>> Is this a temporary position, as the sudo safe.directory problem is
>> still to be added to next?
> yes, it should be fixed once/if that branch graduates to next, and it
> is currently broken in master and all maint branches as well as the
> last 2 releases from those.
>
> Carlo
Thanks for clarifying. Wasn't sure if it was finger trouble on my side.
P.
next prev parent reply other threads:[~2022-05-15 11:38 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 [this message]
2022-05-15 16:51 ` 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=7515c5df-a547-c4dc-5221-0f5089f2a2c3@iee.email \
--to=philipoakley@iee.email \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
/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).