Re: Cygwin Git thinks files are changed when they aren't

2015-03-24 21:42 GMT+01:00 Chloe: > Cygwin Git always thinks files are changed even when they aren't. After a > commit with a Windows Git, Cygwin Git shows files as modified. > [snip] > $ git diff .project > diff --git a/.project b/.project > old mode 100644 > new mode 100755 Apart from the file m

Re: Cygwin Git thinks files are changed when they aren't

Chloe writes: > Cygwin Git always thinks files are changed even when they > aren't. After a commit with a Windows Git, Cygwin Git shows files as > modified. Then either don't mix Cygwin's and whatever Windows' Git you're using or tell Git to ignore the mode bits altogether (check the documentation

Re: Cygwin Git thinks files are changed when they aren't

On 3/24/2015 5:50 PM, Yaakov Selkowitz wrote: > On Tue, 2015-03-24 at 16:42 -0400, Chloe wrote: >> Cygwin Git always thinks files are changed even when they aren't. After >> a commit with a Windows Git, Cygwin Git shows files as modified. > [snip] >> $ git diff .project >> diff --git a/.project b/

Re: Cygwin Git thinks files are changed when they aren't

On Tue, 2015-03-24 at 16:42 -0400, Chloe wrote: > Cygwin Git always thinks files are changed even when they aren't. After > a commit with a Windows Git, Cygwin Git shows files as modified. [snip] > $ git diff .project > diff --git a/.project b/.project > old mode 100644 > new mode 100755 This is

Cygwin Git thinks files are changed when they aren't

Cygwin Git always thinks files are changed even when they aren't. After a commit with a Windows Git, Cygwin Git shows files as modified. Windows Git -- C:\Users\Chloe\workspace\AffiliateArbitrage>git status On branch master nothing to commit, working directory clean C:\U