From: Andreas Ericsson <ae@op5.se>
To: rkitover@io.com
Cc: git@vger.kernel.org
Subject: Re: ignoring file modes completely
Date: Sat, 05 Feb 2011 17:58:49 +0100 [thread overview]
Message-ID: <4D4D81C9.5080002@op5.se> (raw)
In-Reply-To: <4D4D7636.7090608@io.com>
On 02/05/2011 05:09 PM, Rafael Kitover wrote:
> On 2/5/2011 11:03 AM, Jared Hance wrote:
>> On Sat, 2011-02-05 at 10:24 -0500, Rafael Kitover wrote:
>>> Hello,
>>>
>>> I found the core.filemode option, which ignores executable bits, but I
>>> need an option to ignore all mode differences, and such an option does
>>> not seem to exist.
>>
>> The only mode tracked by Git is the executable bit, so this shouldn't
>> even be an issue. Are you sure the executable bit isn't the problem?
>>
> $ git config --global core.filemode
> false
>
> Output of "git diff HEAD" :
>
> diff --git a/Makefile.PL b/Makefile.PL
> old mode 100755
> new mode 100644
> diff --git a/t/02ads.t b/t/02ads.t
> old mode 100755
> new mode 100644
> diff --git a/t/02cxn.t b/t/02cxn.t
> old mode 100755
> new mode 100644
> diff --git a/t/04os.t b/t/04os.t
> old mode 100755
> new mode 100644
Those are all executable bit diffs.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2011-02-05 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 15:24 ignoring file modes completely Rafael Kitover
2011-02-05 16:03 ` Jared Hance
2011-02-05 16:09 ` Rafael Kitover
2011-02-05 16:58 ` Andreas Ericsson [this message]
2011-02-05 19:28 ` Rafael Kitover
2011-02-06 13:14 ` Michael J Gruber
2011-02-06 15:53 ` Rafael Kitover
2011-02-06 16:14 ` Rafael Kitover
2011-02-06 18:10 ` Dmitry Potapov
2011-02-06 20:29 ` Rafael Kitover
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=4D4D81C9.5080002@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=rkitover@io.com \
/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).