From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Martin Langhoff" <martin@catalyst.net.nz>, git@vger.kernel.org
Subject: Re: [PATCH] Introducing cg-xxdiff for conflict resolution
Date: Sun, 24 Sep 2006 18:22:35 +0100 [thread overview]
Message-ID: <46a038f90609241022i6ac11da1o1a1cba199595d036@mail.gmail.com> (raw)
In-Reply-To: <20060924171246.GY13132@pasky.or.cz>
On 9/24/06, Petr Baudis <pasky@suse.cz> wrote:
> In that case I think the most natural way for this tool to interface
> would be in part of some kind of cg-resolve swiss-army knife for
> resolving conflicts:
>
> cg-resolve --mine for taking just the version from _my_
> side of the merge
> cg-resolve --other dtto for the other side of the merge
> cg-resolve -g graphically resolve
> (vimdiff/xxdiff/meld/...)
> surely more would be invented over time
Sounds reasonable. But I think we have to keep in mind that you only
know if the conflict is nasty after you have a go at fixing it. And I
sometimes find that I try with cg-xxdiff... and I go back to the plain
old conflict. That is why it doesn't clobber the file -- to protect a
manual merge in process.
> Well, all the Cogito scripts should have some consistent form. :-)
heh - consistency? overrated! ;-)
> But I can adjust such details when applying your patch.
Great! -- I'm travelling and at an airport "free access" computer. It
should be illegal to run airports without free wifi in this day and
age.
cheers,
martin
next prev parent reply other threads:[~2006-09-24 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 3:34 [PATCH] Introducing cg-xxdiff for conflict resolution Martin Langhoff
2006-09-24 16:50 ` Petr Baudis
2006-09-24 17:02 ` Martin Langhoff
2006-09-24 17:12 ` Petr Baudis
2006-09-24 17:22 ` Martin Langhoff [this message]
2006-09-24 17:28 ` Petr Baudis
2006-11-02 23:40 ` Martin Langhoff
2006-11-03 0:11 ` Petr Baudis
2006-11-03 2:41 ` Martin Langhoff
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=46a038f90609241022i6ac11da1o1a1cba199595d036@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin@catalyst.net.nz \
--cc=pasky@suse.cz \
/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).