git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Forrest <nobozo@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Torsten Bögershausen" <tboegi@web.de>,
	git@vger.kernel.org
Subject: Re: Odd Difference Between Windows Git and Standard Git
Date: Mon, 23 May 2016 17:08:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1605231700380.4449@virtualbox> (raw)
In-Reply-To: <6e4862b8-b5ab-ced4-29a0-bf975848e98f@gmail.com>

Hi Jon,

On Mon, 23 May 2016, Jon Forrest wrote:

> On 5/23/2016 4:12 AM, Johannes Schindelin wrote:
> 
> > What we could do is to make the default config setting platform-dependent,
> > a la CRLF_NATIVE.
> >
> > I imagine that we would want this for core.filemode, core.ignorecase and
> > core.symlinks.
> >
> > What do you think?
> 
> Would this change have any bad effects when the same repo is shared
> by both Windows and *nix Git users over Dropbox or a shared filesystem?

Yes, if you have symbolic links in that repository. Likewise, if you have
users who find it funny to add different files whose names only differ in
their case, say, xt_DSCP.c and xt_dscp.c.

Also, if your Windows users want to add scripts, they will most likely not
mark them executable and your Linux users will call them names (forgetting
that they know just as little about the other platform as the developers
they try to ridicule).

Lots of fun things to keep in mind when sharing the same working directory
between Operating Systems.

But you said "when the same repo is shared"? Do you really mean the
*repository*? If so, there is not a problem. Only if you add a working
directory into the mix.

Ciao,
Johannes

  reply	other threads:[~2016-05-23 15:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  1:48 Odd Difference Between Windows Git and Standard Git Jon Forrest
2016-05-20 13:19 ` Torsten Bögershausen
2016-05-20 13:48   ` Jon Forrest
2016-05-20 14:19     ` Torsten Bögershausen
2016-05-20 14:28       ` Jon Forrest
2016-05-20 15:57         ` Torsten Bögershausen
2016-05-20 15:23       ` Junio C Hamano
2016-05-20 16:12         ` Torsten Bögershausen
2016-05-20 16:21         ` Junio C Hamano
2016-05-23 11:12           ` Johannes Schindelin
2016-05-23 13:44             ` Jon Forrest
2016-05-23 15:08               ` Johannes Schindelin [this message]
2016-05-23 18:52             ` Junio C Hamano
2016-05-24  4:52               ` Torsten Bögershausen
2016-05-24 11:57                 ` Johannes Schindelin
2016-05-25  4:36                   ` Torsten Bögershausen
2016-05-25 11:52                     ` Johannes Schindelin

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=alpine.DEB.2.20.1605231700380.4449@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nobozo@gmail.com \
    --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 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).