From: Carl Worth <cworth@cworth.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Avoiding uninteresting merges in Cairo
Date: Thu, 14 Dec 2006 20:01:13 -0800 [thread overview]
Message-ID: <87slfh4xkm.wl%cworth@cworth.org> (raw)
In-Reply-To: <20061215032530.GM26202@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
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@example.com
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 #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-15 4:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:06 Avoiding uninteresting merges in Cairo Shawn Pearce
2006-12-15 3:17 ` Carl Worth
2006-12-15 3:25 ` Shawn Pearce
2006-12-15 4:01 ` Carl Worth [this message]
2006-12-15 7:53 ` Shawn Pearce
2006-12-15 14:21 ` Jakub Narebski
2006-12-15 15:01 ` Shawn Pearce
2006-12-15 15:57 ` Jakub Narebski
2006-12-15 16:03 ` Shawn Pearce
2006-12-15 16:53 ` [PATCH] gitweb: Do not show difftree for merges in "commit" view Jakub Narebski
2006-12-15 21:03 ` Avoiding uninteresting merges in Cairo Junio C Hamano
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=87slfh4xkm.wl%cworth@cworth.org \
--to=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).