From: "Brett Simmers" <swtaarrs@gmail.com>
To: rdkrsr <rdkrsr@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: after first git clone of linux kernel repository there are changed files in working dir
Date: Wed, 10 Dec 2008 15:20:16 -0500 [thread overview]
Message-ID: <e32b7bb40812101220s370a64f1n3f7ecb56dd352405@mail.gmail.com> (raw)
In-Reply-To: <d304880b0812101022u2abe5d68ub3bda68ed39f830b@mail.gmail.com>
On Wed, Dec 10, 2008 at 1:22 PM, rdkrsr <rdkrsr@googlemail.com> wrote:
> I just fetched the sources without changing anything, but git diff
> shows, that there are changes that are not yet updated (changed but not
> updated: use git add to ...). Why is it like that?
>
> I use msysgit on windows, maybe that is one reason?
What are the filenames? I've seen git on Windows get confused if a
repository has two files that are the same except for the case of some
of the letters (since both can't exist by default on NTFS).
-Brett
next prev parent reply other threads:[~2008-12-10 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d304880b0812101019ufe85095h46ff0fe00d32bbd0@mail.gmail.com>
2008-12-10 18:22 ` after first git clone of linux kernel repository there are changed files in working dir rdkrsr
2008-12-10 20:20 ` Brett Simmers [this message]
[not found] ` <d304880b0812110142g41b80745ic09a7200e02dcdb0@mail.gmail.com>
2008-12-11 17:15 ` Fwd: " rdkrsr
2008-12-11 17:41 ` Linus Torvalds
2008-12-11 17:58 ` rdkrsr
2008-12-11 20:23 ` Boyd Stephen Smith Jr.
2008-12-11 20:35 ` Giuseppe Bilotta
2008-12-12 13:51 ` Nick Andrew
2009-01-19 13:36 ` Hannu Koivisto
2009-01-19 23:52 ` An idea: maybe Git should use a lock/unlock file mode for problematic files? [Was: Re: after first git clone of linux kernel repository there are changed files in working dir] thestar
2009-01-20 20:11 ` Daniel Barkalow
2009-01-20 21:28 ` John Chapman
2009-01-20 22:08 ` Daniel Barkalow
2009-01-20 23:25 ` Alex Riesen
2009-01-21 0:03 ` Daniel Barkalow
2009-01-21 7:25 ` Alex Riesen
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=e32b7bb40812101220s370a64f1n3f7ecb56dd352405@mail.gmail.com \
--to=swtaarrs@gmail.com \
--cc=git@vger.kernel.org \
--cc=rdkrsr@googlemail.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).