Re: Odd Difference Between Windows Git and Standard Git

Hi Torsten, On Wed, 25 May 2016, Torsten Bögershausen wrote: > On 05/24/2016 01:57 PM, Johannes Schindelin wrote: > > > > On Tue, 24 May 2016, Torsten Bögershausen wrote: > > > > > if core.filemode is true, Git for Windows could: > > > a) Behave as today, report changed files (filemode) > > > b)

Re: Odd Difference Between Windows Git and Standard Git

On 05/24/2016 01:57 PM, Johannes Schindelin wrote: Hi, On Tue, 24 May 2016, Torsten Bögershausen wrote: On 05/23/2016 08:52 PM, Junio C Hamano wrote: Johannes Schindelin writes: Of course, if you are doing network mount between systems with and without filemode

Re: Odd Difference Between Windows Git and Standard Git

Hi, On Tue, 24 May 2016, Torsten Bögershausen wrote: > On 05/23/2016 08:52 PM, Junio C Hamano wrote: > > Johannes Schindelin writes: > > > > > > Of course, if you are doing network mount between systems with and > > > > without filemode support, the result would

Re: Odd Difference Between Windows Git and Standard Git

On 05/23/2016 08:52 PM, Junio C Hamano wrote: Johannes Schindelin writes: Of course, if you are doing network mount between systems with and without filemode support, the result would depend on where you did the "git init", so that would not help. Which means that

Re: Odd Difference Between Windows Git and Standard Git

Johannes Schindelin writes: >> Of course, if you are doing network mount between systems with and >> without filemode support, the result would depend on where you did >> the "git init", so that would not help. >> >> Which means that other probed things like symlink

Re: Odd Difference Between Windows Git and Standard Git

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 > >

Re: Odd Difference Between Windows Git and Standard Git

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

Re: Odd Difference Between Windows Git and Standard Git

Hi, On Fri, 20 May 2016, Junio C Hamano wrote: > Junio C Hamano writes: > > > Thanks for asking a great question. I somehow expected that we > > probe in init-db.c::create_default_files() for this when we probe > > for case sensitivity, symlinks, etc., but apparently we

Re: Odd Difference Between Windows Git and Standard Git

Junio C Hamano writes: > Thanks for asking a great question. I somehow expected that we > probe in init-db.c::create_default_files() for this when we probe > for case sensitivity, symlinks, etc., but apparently we don't. Ah, we do probe by using "config" as a guinea pig

Re: Odd Difference Between Windows Git and Standard Git

On 20.05.16 17:23, Junio C Hamano wrote: > Torsten Bögershausen writes: > What does git diff say ? >>> >>> Great question. For all the unexpected files it says the >>> same thing: >>> >>> old mode 100755 >>> new mode 100644 >> >> So the solution is to run >> git

Re: Odd Difference Between Windows Git and Standard Git

On 20.05.16 16:28, Jon Forrest wrote: > > > On 5/20/2016 7:19 AM, Torsten Bögershausen wrote: > >>> Great question. For all the unexpected files it says the >>> same thing: >>> >>> old mode 100755 >>> new mode 100644 >> >> So the solution is to run >> git config core.filemode false > > This

Re: Odd Difference Between Windows Git and Standard Git

Torsten Bögershausen writes: >>> What does >>> git diff >>> say ? >> >> Great question. For all the unexpected files it says the >> same thing: >> >> old mode 100755 >> new mode 100644 > > So the solution is to run > git config core.filemode false Thanks for asking a great

Re: Odd Difference Between Windows Git and Standard Git

On 5/20/2016 7:19 AM, Torsten Bögershausen wrote: Great question. For all the unexpected files it says the same thing: old mode 100755 new mode 100644 So the solution is to run git config core.filemode false This worked perfectly! I wonder if this should be the default for Git for

Re: Odd Difference Between Windows Git and Standard Git

On 20.05.16 15:48, Jon Forrest wrote: > > > On 5/20/2016 6:19 AM, Torsten Bögershausen wrote: >> On 20.05.16 03:48, Jon Forrest wrote: >>> I'm running Git version 2.8.2 built from source on Ubuntu 16.04. >>> I'm using a repository that's stored on Dropbox. I'm the only person >>> accessing this

Re: Odd Difference Between Windows Git and Standard Git

On 5/20/2016 6:19 AM, Torsten Bögershausen wrote: On 20.05.16 03:48, Jon Forrest wrote: I'm running Git version 2.8.2 built from source on Ubuntu 16.04. I'm using a repository that's stored on Dropbox. I'm the only person accessing this repo. Everything works great. For reasons unrelated to

Re: Odd Difference Between Windows Git and Standard Git

On 20.05.16 03:48, Jon Forrest wrote: > I'm running Git version 2.8.2 built from source on Ubuntu 16.04. > I'm using a repository that's stored on Dropbox. I'm the only person > accessing this repo. Everything works great. > > For reasons unrelated to Git, I decided to try Git for Windows, > so I

Odd Difference Between Windows Git and Standard Git

I'm running Git version 2.8.2 built from source on Ubuntu 16.04. I'm using a repository that's stored on Dropbox. I'm the only person accessing this repo. Everything works great. For reasons unrelated to Git, I decided to try Git for Windows, so I installed "git version 2.8.2.windows.1" on