public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: Cygwin Git thinks files are changed when they aren't
Date: Wed, 25 Mar 2015 06:32:00 -0000	[thread overview]
Message-ID: <55125353.7030003@jhmg.net> (raw)
In-Reply-To: <1427244613.3752.4.camel@cygwin.com>

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/.project
>> old mode 100644
>> new mode 100755
> 
> This is your answer.  On Windows, everything is executable, so changing
> a file with any native Windows program is bound to set the executable
> bit.  A change in permissions is considered a modification in git, hence
> the message.
> 
> To avoid this, you'll probably have to git clone with your Windows git
> to start with, as Cygwin programs won't change the permissions unless
> you tell them to.

See http://stackoverflow.com/questions/1580596

git config core.fileMode false


-- 
Jim Garrison (jhg@acm.org)
PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-03-25  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 21:24 Chloe
2015-03-25  2:01 ` Yaakov Selkowitz
2015-03-25  6:32   ` Jim Garrison [this message]
2015-03-25  6:34 ` Achim Gratz
2015-03-25 11:20 ` Frank Fesevur

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=55125353.7030003@jhmg.net \
    --to=jhg@jhmg.net \
    --cc=cygwin@cygwin.com \
    --cc=jhg@acm.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).