On Thu, 14 Dec 2006 22:25:30 -0500, Shawn Pearce wrote: > I saw three things happen to poor jwatt that really threw him for > a loop, and I think they are all more likely related to Git than > to the Cairo project specifically: Yes. Also a fourth one was a filesystem case-insensitivity issue. We recently imported an external library into cairo that had some filenames with capital letters. We then renamed them to the all-lowercase filenames we like. Poor jwatt was unlucky enough to have cloned with a capitalized filename, and then was trying to pull the latest with the lowercase filename and he got: fatal: Untracked working tree file 'test/pdiff/lpyramid.h' would be overwritten by merge This was in some sense worse than the other problems since it stopped him cold and gave him no idea what was wrong nor how to fix it. > * His user.name/user.email is probably not what he wanted; > > * His Cygwin/Windows system made some *.c/*.c files 0755 without > him realizing it; Those two issues did silently put garbage in the commits. I don't know how to best fix the name/email thing. Maybe on the first commit with no user.name and user.email configuration git could create them, announce them to the user, and instruct them on how to change them: No name or email configuration exists. Using: U-JONATHAN-X60S\jonathan <jonathan@Jonathan-X60s.(none)> You can change these with the following commands: git repo-config user.name Your Name git repo-config user.email user@xxxxxxxxxxx And maybe mention --global as well. As for the filemode setting, shouldn't that be configured by default the right way for Windows git? > * gitweb made it appear as though a whole lot of Carl's recent > work was somehow undone in the merge. That looks like a simple gitweb bug. None of the other tools, (gitk, git log -p), consider a trivial merge commit like this as having anything interesting in it worth displaying. -Carl
Attachment:
pgpo3x0yWa2FI.pgp
Description: PGP signature