From: Jonathan del Strother <maillist@steelskies.com>
To: Junio C Hamano <gitster@pobox.com>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Merging adjacent deleted lines?
Date: Thu, 22 Jan 2009 10:57:41 +0000 [thread overview]
Message-ID: <57518fd10901220257p62b6d1efof97ba3fcf90dbfda@mail.gmail.com> (raw)
In-Reply-To: <7vy6x4cqq1.fsf@gitster.siamese.dyndns.org>
On Wed, Jan 21, 2009 at 7:49 PM, Robin Rosenberg
<robin.rosenberg.lists@dewire.com> wrote:
> onsdag 21 januari 2009 20:20:50 skrev Jonathan del Strother:
> [...]
> I think you've illustrated a case for graphical merge resolution tools, i.e.
> run git mergetool to help resolve the conlicts. It will run a graphical tool
> for you.
>
Mmm. I use opendiff, which is generally ok, but in this case produced
a merge looking like this :
http://pastie.org/paste/asset/367587/Picture_6.png
Which, in my mind, isn't any clearer about the fact that both lines
ought to be deleted than the text conflict markers are. Do any of the
other graphical tools present conflicts like that differently?
On Wed, Jan 21, 2009 at 9:08 PM, Junio C Hamano <gitster@pobox.com> wrote:
> But that is only true if it is obvious to you. When you cannot remember
> what each side did since they forked, there are two ways you can use to
> understand the history better without resorting to graphical merge tools.
>
> $ git log -p --merge <path>
>
Ahh, that's very helpful - thanks.
next prev parent reply other threads:[~2009-01-22 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 19:20 Merging adjacent deleted lines? Jonathan del Strother
2009-01-21 19:49 ` Robin Rosenberg
2009-01-21 21:08 ` Junio C Hamano
2009-01-22 10:57 ` Jonathan del Strother [this message]
2009-01-22 20:13 ` Robin Rosenberg
2009-01-23 7:18 ` Jay Soffian
2009-01-23 10:32 ` Robin Rosenberg
2009-01-23 15:51 ` Jay Soffian
2009-01-23 15:59 ` Jay Soffian
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=57518fd10901220257p62b6d1efof97ba3fcf90dbfda@mail.gmail.com \
--to=maillist@steelskies.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.com \
/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).