From: "David Aguilar" <davvid@gmail.com>
To: "Caleb Cushing" <xenoterracide@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git has modified files after clean checkout
Date: Wed, 31 Dec 2008 15:41:36 -0800 [thread overview]
Message-ID: <402731c90812311541v28ac9617ge52e0e5c0f1298d2@mail.gmail.com> (raw)
In-Reply-To: <81bfc67a0812311223g2b6e8476y84b23c19977dfd10@mail.gmail.com>
On Wed, Dec 31, 2008 at 12:23 PM, Caleb Cushing <xenoterracide@gmail.com> wrote:
> here's what I did
>
> rm -r portage
> git clone git@github.com:xenoterracide/portage.git
Here's the anonymous clone URL (the one you provided is private)
$ git clone git://github.com/xenoterracide/portage.git
Read on below...
> cd portage
> git checkout origin/regen2 -b regen2
> git status
>
> # On branch regen2
> # Changed but not updated:
> # (use "git add <file>..." to update what will be committed)
> #
> # modified:
> x11-themes/metacity-themes/files/metacity-themes-1.0-gentoo.diff
> # modified:
> x11-themes/metacity-themes/files/metacity-themes-1.2-gentoo.diff
> #
> no changes added to commit (use "git add" and/or "git commit -a")
>
> why are there files claiming to be modified? this is a clean clone.
> I've had this before I usually end up doing a git reset --hard HEAD,
> but I'm thinking it's a bug, since I've seen it vary on the same clone
> and sometimes even disappear.
>
> git version 1.6.0.6
> --
> Caleb Cushing
>
> http://xenoterracide.blogspot.com
I followed the steps above and did not run into any such issues.
$ git status
# On branch regen2
nothing to commit (working directory clean)
$ git version
git version 1.6.1.28.gc32f76
(Junio's latest master at the moment)
Here's my quick guess based on what I'm seeing --
The files you mention contain CRLF. Do you have core.autocrlf set
globally somewhere, perhaps in your ~/.gitconfig?
It's possible that the autocrlf stuff is messing with those files.
They seem to be a mix of both unix LF and CRLF (the CRLF stuff doesn't
start until line 104 of
x11-themes/metacity-themes/files/metacity-themes-1.0-gentoo.diff, for
example, which is kinda odd but maybe be intentional?)
Check your autocrlf settings.
The following commands print out nothing for me:
$ git config core.autocrlf
$ git config --global core.autocrlf
Anyways.. like I said -- I couldn't reproduce your problem so this is
pure speculation on my part =)
Good luck,
--
David
next prev parent reply other threads:[~2008-12-31 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 20:23 git has modified files after clean checkout Caleb Cushing
2008-12-31 23:41 ` David Aguilar [this message]
2009-01-01 8:48 ` Caleb Cushing
2009-01-01 19:48 ` Thomas Rast
2009-01-02 5:49 ` Caleb Cushing
2009-01-05 5:11 ` Caleb Cushing
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=402731c90812311541v28ac9617ge52e0e5c0f1298d2@mail.gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=xenoterracide@gmail.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).