git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Michael Ludwig <michael.ludwig@xing.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git status showing phantom modifications
Date: Wed, 27 Jan 2010 13:14:39 +0800	[thread overview]
Message-ID: <be6fef0d1001262114r137ba8ddi60a3a3468950c5ce@mail.gmail.com> (raw)
In-Reply-To: <59B5C4C4-6E95-4BAA-9351-B88B6309E022@xing.com>

Hi Johannes,

do you happen to have any clue on this?

-- 
Cheers,
Ray Chuan


On Tue, Jan 26, 2010 at 5:14 PM, Michael Ludwig <michael.ludwig@xing.com> wrote:
> Am 25.01.2010 um 12:43 schrieb Michael Ludwig:
>
>> Reading up about core.fileMode in git-config(1), I think you've pointed
>> me to the solution. I should probably just set it to false. If that doesn't
>> solve the issue, I'll report back.
>
> Back with more info:
>
> git version 1.6.4.2
>
> Before adding any core.filemode setting to ~/.gitconfig or .git/config:
>
> michael@wladimir:/cygdrive/m/REPOS6.TECH.git/comp :-) git config -l
> user.name=Michael Ludwig
> user.email=...
> core.repositoryformatversion=0
> core.filemode=true                      <= filemode already present
> core.bare=false
> core.logallrefupdates=true
> core.ignorecase=true
> core.autocrlf=false
> svn-remote.svn.ignore-paths=^(some|paths)
> svn-remote.svn.url=svn://localhost
> svn-remote.svn.fetch=:refs/remotes/git-svn
> svn.authorsfile=authors.txt
>
> My git status output after cd to subdir shows many files "modified". But
> they aren't! Edited ~/.gitconfig to include core.filemode = true [sic].
> Here's the diff for the git config output:
>
> --- /home/michael/a     2010-01-25 20:36:53.140625000 +0100
> +++ /home/michael/b     2010-01-25 20:37:01.421875000 +0100
> @@ -4,6 +4,7 @@
> alias.ci=checkin
> alias.co=checkout
> alias.br=branch
> +core.filemode=true
> core.repositoryformatversion=0
> core.filemode=true
> core.bare=false
>
> We're seeing core.filemode appear *twice*. Why that?
>
> michael@wladimir:/cygdrive/m/REPOS6.TECH.git/comp :-) git st
> # On branch master
> nothing to commit (working directory clean)
>
> So it seems adding core.filemode = true has fixed the issue, or at least
> covered the symptoms. Adding core.filemode = false did not cause the
> phantom modifications to disappear. Note that from reading git-config(1),
> I had rather assumed this latter setting to have the desired effect.
>
> And something seems to be wrong here. Why are modifications flagged when
> doing git status from a subdir but not from the topdir?
>
> --
> Michael.Ludwig (#) XING.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2010-01-27  5:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 10:41 git status showing phantom modifications Michael Ludwig
2010-01-25 11:03 ` Tay Ray Chuan
2010-01-25 11:43   ` Michael Ludwig
2010-01-26  9:14     ` Michael Ludwig
2010-01-27  5:14       ` Tay Ray Chuan [this message]
2010-01-27  7:20         ` Johannes Sixt
2010-01-28  8:45           ` Michael Ludwig

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=be6fef0d1001262114r137ba8ddi60a3a3468950c5ce@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=michael.ludwig@xing.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).