From: Michael J Gruber <git@drmicha•warpmail.net>
To: rkitover@io•com
Cc: git@vger•kernel.org, Andreas Ericsson <ae@op5•se>, jaredhance@gmail•com
Subject: Re: ignoring file modes completely
Date: Sun, 06 Feb 2011 14:14:20 +0100 [thread overview]
Message-ID: <4D4E9EAC.4030508@drmicha.warpmail.net> (raw)
In-Reply-To: <4D4DA4C1.5050501@io.com>
Rafael Kitover venit, vidit, dixit 05.02.2011 20:28:
> On 2/5/2011 11:58 AM, Andreas Ericsson wrote:
>> 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.
>>
>
> Ok, but I have core.filemode set to "false" as I showed, why does this
> happen then?
I can't confirm this on linux with current git. What are your versions?
Do you have a minimal example (starting from git init)?
Michael
BTW: Leaving out helpful folks from cc does not help... I should not
have to re-add them by hand.
next prev parent reply other threads:[~2011-02-06 13:13 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
2011-02-05 19:28 ` Rafael Kitover
2011-02-06 13:14 ` Michael J Gruber [this message]
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=4D4E9EAC.4030508@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=ae@op5$(echo .)se \
--cc=git@vger$(echo .)kernel.org \
--cc=jaredhance@gmail$(echo .)com \
--cc=rkitover@io$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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