All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Marcos Del Sol Vives <marcos@orca.pet>,  git <git@vger.kernel.org>
Subject: Re: Permission issue in Git in DrvFs-mounted network drives
Date: Fri, 20 Sep 2024 11:15:42 -0700	[thread overview]
Message-ID: <xmqqsetugpip.fsf@gitster.g> (raw)
In-Reply-To: <Zu2aHdaw_oDv_dp7@tapette.crustytoothpaste.net> (brian m. carlson's message of "Fri, 20 Sep 2024 15:51:57 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> Other folks may feel differently about fixing this, but I would suggest
> against it.
>
>> The WSL team at Microsoft has been already informed as well:
>> https://github.com/microsoft/WSL/issues/12051
>
> I've provided some comments in the issue there.
>
> [0] https://pubs.opengroup.org/onlinepubs/9799919799/functions/open.html

It depends on how hard it would be for filesystem providers to fix
their ware, but (1) leaving our code to require open semantics of
POSIX may serve as an incentive to encourage them to do so, and (2)
I am not fundamentally opposed to have an option to help users of
such flawed filesystem, provided if such a change is done cleanly.

Thanks.

  reply	other threads:[~2024-09-20 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 16:16 Permission issue in Git in DrvFs-mounted network drives Marcos Del Sol Vives
2024-09-18 16:30 ` rsbecker
2024-09-18 16:38   ` Marcos Del Sol Vives
2024-09-20 15:51 ` brian m. carlson
2024-09-20 18:15   ` Junio C Hamano [this message]
2024-09-20 18:36     ` Marcos Del Sol Vives
2024-09-20 20:43       ` brian m. carlson
2024-09-20 22:39         ` Marcos Del Sol Vives
2024-09-21 11:20           ` brian m. carlson

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=xmqqsetugpip.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=marcos@orca.pet \
    --cc=sandals@crustytoothpaste.net \
    /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.