From: Wink Saville <wink@saville.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git <git@vger.kernel.org>
Subject: Re: Resolving conflicts
Date: Thu, 30 Nov 2006 23:52:04 -0800 [thread overview]
Message-ID: <456FDF24.1070001@saville.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611302330000.3695@woody.osdl.org>
Linus Torvalds wrote:
>
> On Thu, 30 Nov 2006, Wink Saville wrote:
>> I then searched the net for how to resolve conflicts, seems you
>> should start by doing a git-diff, so I did and I get this:
>>
>> diff --cc kernel/fork.c
>> index d74b4a5,8cdd3e7..0000000
>> --- a/kernel/fork.c
>> +++ b/kernel/fork.c
>> diff --cc kernel/spinlock.c
>> index f4d1718,2c6c2bf..0000000
>> --- a/kernel/spinlock.c
>> +++ b/kernel/spinlock.c
>
> Hmm. That doesn't look like a conflict. If it had a real conflict, I'd
> have expected to see it mentioned in that diff..
>
> This may be a stupid question, but if you haven't actually ever needed to
> do any file-level merges before, this may be the first time you've
> actually had the external 3-way "merge" program called, and that's one of
> the few things that git still depends on _external_ programs for. And if
> that program is broken or missing, you'd get bubkis.
>
> (This is hopefully getting fixed, and we'll have one less external
> dependency to worry about, but it's the only thing that springs to mind)
>
> That's especially true since the merge-head your log shows wasn't even all
> that long ago: there's just 80 commits since that common merge base, and
> only two of them even change those two files, and only in rather simple
> ways at that.
>
> So my guess is that there wasn't actually a conflict at all, but the
> "merge" program (usually in /usr/bin/merge) returned an error for some
> reason. What does "which merge" and "rpm -qf /usr/bin/merge" say?
>
> But you can also do "git diff --ours" (or "git diff --their") to get a
> simple two-way diff of the end result of the merge to what you were
> looking at.
>
> Linus
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Earlier had a problem with git wanting merge but didn't have it and
couldn't figure out which package it was in Ubuntu:( So I symlinked merge
to kdiff3 which worked at the time:
wink@winkc2d1:~/linux/linux-2.6$ ls -al /usr/bin/merge
lrwxrwxrwx 1 root root 6 2006-11-17 19:24 /usr/bin/merge -> kdiff3
But doesn't/didn't work this time.
I tried "git diff --ours"
wink@winkc2d1:~/linux/linux-2.6$ git diff --ours
* Unmerged path kernel/fork.c
diff --git a/kernel/fork.c b/kernel/fork.c
* Unmerged path kernel/spinlock.c
diff --git a/kernel/spinlock.c b/kernel/spinlock.c
wink@winkc2d1:~/linux/linux-2.6$
Wink
Not too helpful:(
next prev parent reply other threads:[~2006-12-01 7:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 7:06 Resolving conflicts Wink Saville
2006-12-01 7:30 ` Alan Chandler
2006-12-01 7:41 ` Wink Saville
2006-12-01 8:10 ` Alan Chandler
2006-12-01 7:39 ` Linus Torvalds
2006-12-01 7:52 ` Wink Saville [this message]
2006-12-01 7:57 ` Linus Torvalds
2006-12-01 8:00 ` Linus Torvalds
2006-12-01 8:13 ` Alan Chandler
2006-12-01 8:22 ` Wink Saville
2006-12-01 23:47 ` Alan Chandler
2006-12-02 3:04 ` Wink Saville
2006-12-02 4:30 ` Linus Torvalds
2006-12-02 7:55 ` Junio C Hamano
2006-12-02 10:49 ` using xdl_merge(), was " Johannes Schindelin
2006-12-05 17:58 ` Ramsay Jones
2006-12-05 18:28 ` Linus Torvalds
2006-12-05 18:43 ` Junio C Hamano
2006-12-05 18:53 ` Johannes Schindelin
2006-12-05 19:50 ` Junio C Hamano
2006-12-05 21:15 ` [PATCH] xdl_merge(): fix and simplify conflict handling Johannes Schindelin
2006-12-05 22:10 ` Junio C Hamano
2006-12-05 22:24 ` Johannes Schindelin
2006-12-05 22:54 ` Junio C Hamano
2006-12-05 22:27 ` Jakub Narebski
2006-12-05 22:27 ` Johannes Schindelin
2006-12-06 9:48 ` using xdl_merge(), was Re: Resolving conflicts Junio C Hamano
2006-12-06 10:02 ` Johannes Schindelin
2006-12-06 10:13 ` Junio C Hamano
2006-12-06 10:47 ` Johannes Schindelin
2006-12-05 18:36 ` Johannes Schindelin
2006-12-01 7:53 ` Linus Torvalds
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=456FDF24.1070001@saville.com \
--to=wink@saville.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).