On Sun, Feb 13, 2011 at 3:32 PM, John Collins <[email protected]> wrote: > On 02/13/2011 03:28 PM, jd wrote: >> I have a usb drive (flash drive, FAT32, Windows) with all sorts of >> stuff, including a handful of git repositories. I recently copied the >> whole drive over to a newer usb drive. I then went to one of the >> repositories on the new driveand did a 'git status' and was told that >> dozens of files had changed (but they really hadn't). I know that >> 'git clone' is the proper way clone a repository, but why wouldn't a >> copy work properly? > > Probably because the dates have changed.
Usually that just makes 'git status' take extra long the first time, but get fast afterwards. However, git on Windows is still a little funny, so maybe something like that is the cause. More often it's crlf (line endings) related; did you happen to install a new copy of git or change your crlf default setting? If you run 'git checkout .' it should fix all the attributes after grinding away for a while. (But watch out; if you really *have* changed any files, the changes will be lost.) Have fun, Avery -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
