From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Madhu <enometh@meer.net>, git@vger.kernel.org
Subject: Re: [PATCH] init: don't reset core.filemode on git-new-workdirs.
Date: Tue, 23 Mar 2021 13:50:46 -0700 [thread overview]
Message-ID: <xmqqr1k51tnd.fsf@gitster.g> (raw)
In-Reply-To: <20210323203124.oxzqad2wmedelstu@tb-raspi4> ("Torsten Bögershausen"'s message of "Tue, 23 Mar 2021 21:31:24 +0100")
Torsten Bögershausen <tboegi@web.de> writes:
>> I do not think we want to go there. filemode is not the only thing
>> that would be shared. What do you want to do with core.eol=native,
>> for example? Paths touched while switching branches get the 'native'
>> line endings on the system that the user happened to be on when the
>> "switch" command was run, and working tree files end up with mixture?
>
> I don't intend to solve all possible confusions caused by sharing all
> config variables - just this very one.
I intend to help users by drawing a clear red line and telling them
that crossing that line leads them to danger.
Sharing a working tree across systems that require different core.*
settings (filemode included) is on the other side of that line, and
that is the reason why I said I do not think we want to go there.
By saying "this is only about core.filemode but you can share a
working tree between incompatible systems", I am afraid that we end
up training users to go where they should not get nearby.
next prev parent reply other threads:[~2021-03-23 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 12:28 [PATCH] init: don't reset core.filemode on git-new-workdirs Madhu
2021-03-21 21:58 ` Junio C Hamano
2021-03-22 2:40 ` Madhu
2021-03-22 4:53 ` Junio C Hamano
2021-03-22 9:04 ` Madhu
2021-03-22 18:02 ` Junio C Hamano
2021-03-23 3:57 ` Madhu
2021-03-23 6:39 ` Junio C Hamano
2021-03-23 16:53 ` Torsten Bögershausen
2021-03-23 17:45 ` Junio C Hamano
2021-03-23 20:31 ` Torsten Bögershausen
2021-03-23 20:50 ` Junio C Hamano [this message]
2021-06-18 4:18 ` Madhu
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=xmqqr1k51tnd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=enometh@meer.net \
--cc=git@vger.kernel.org \
--cc=tboegi@web.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 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.