git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 0/2] mingw: special-case administrators even more
Date: Tue, 25 Mar 2025 10:38:28 +0000	[thread overview]
Message-ID: <pull.1893.git.1742899110.gitgitgadget@gmail.com> (raw)

On Windows, a file created by a process running in elevated mode is owned by
the Administrators group (not by the user's account who would otherwise be
able to modify or delete the file in non-elevated mode). Let's adjust the
"safe directory" feature accordingly.

Naturally, this patch series does not add a regression test (because it
can't, you cannot automate elevating processes).

This patch series is a companion of
https://github.com/microsoft/git/pull/712.

Johannes Schindelin (2):
  mingw: special-case administrators even more
  test-tool path-utils: support debugging "dubious ownership" issues

 compat/mingw.c             | 39 +++++++++++++++++++++++++++-----------
 t/helper/test-path-utils.c | 19 +++++++++++++++++++
 2 files changed, 47 insertions(+), 11 deletions(-)


base-commit: 683c54c999c301c2cd6f715c411407c413b1d84e
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1893%2Fdscho%2Fadmins-are-admins-on-windows-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1893/dscho/admins-are-admins-on-windows-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1893
-- 
gitgitgadget

             reply	other threads:[~2025-03-25 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 10:38 Johannes Schindelin via GitGitGadget [this message]
2025-03-25 10:38 ` [PATCH 1/2] mingw: special-case administrators even more Johannes Schindelin via GitGitGadget
2025-03-25 10:38 ` [PATCH 2/2] test-tool path-utils: support debugging "dubious ownership" issues Johannes Schindelin via GitGitGadget

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=pull.1893.git.1742899110.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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).