From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2022, #05; Mon, 16)
Date: Thu, 19 May 2022 10:29:02 -0700 [thread overview]
Message-ID: <xmqqa6bdph29.fsf@gitster.g> (raw)
In-Reply-To: <20220519152344.ktrifm3pc42bjruh@Carlos-MacBook-Pro-2.local> ("Carlo Marcelo Arenas Belón"'s message of "Thu, 19 May 2022 08:23:44 -0700")
Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:
> On Mon, May 16, 2022 at 10:37:04PM -0700, Junio C Hamano wrote:
>>
>> * cb/path-owner-check-with-sudo (2022-05-12) 4 commits
>> - git-compat-util: allow root to access both SUDO_UID and root owned
>> - t0034: add negative tests and allow git init to mostly work under sudo
>> - git-compat-util: avoid failing dir ownership checks if running privileged
>> - t: regression git needs safe.directory when using sudo
>>
>> With a recent update to refuse access to repositories of other
>> people by default, "sudo make install" and "sudo git describe"
>> stopped working. This series intends to loosen it while keeping
>> the safety.
>>
>> Will merge to 'next'?
>> source: <20220513010020.55361-1-carenas@gmail.com>
>
> I am obviously biased, and probably confused, since this is already in the
> "cooking" section, but I think this is ready and should be merged to next
> without the optional patch 4.
I agree that #4 may be subject to further discussion, but the other
three are solid enough. Let's merge it down.
Thanks.
next prev parent reply other threads:[~2022-05-19 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 5:37 What's cooking in git.git (May 2022, #05; Mon, 16) Junio C Hamano
2022-05-17 13:10 ` Derrick Stolee
2022-05-20 23:28 ` Taylor Blau
2022-05-19 15:23 ` Carlo Marcelo Arenas Belón
2022-05-19 17:29 ` Junio C Hamano [this message]
2022-05-19 19:28 ` ab/env-array (was: What's cooking in git.git (May 2022, #05; Mon, 16)) Ævar Arnfjörð Bjarmason
2022-05-19 21:41 ` ab/env-array Junio C Hamano
2022-05-20 8:33 ` ab/env-array Ævar Arnfjörð Bjarmason
2022-05-19 19:34 ` ar/send-email-confirm-by-default (was: What's cooking in git.git (May 2022, #05; Mon, 16)) Ævar Arnfjörð Bjarmason
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=xmqqa6bdph29.fsf@gitster.g \
--to=gitster@pobox.com \
--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).