git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Bailey <charles@hashpling.org>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how do I resolve this merge manually + mergetool bug
Date: Tue, 24 Feb 2009 09:13:30 +0000	[thread overview]
Message-ID: <20090224091330.GB23927@hashpling.org> (raw)
In-Reply-To: <81bfc67a0902240032t783abcabgaf8fa13b2a43e48@mail.gmail.com>

On Tue, Feb 24, 2009 at 03:32:50AM -0500, Caleb Cushing wrote:
> On Tue, Feb 24, 2009 at 2:47 AM, Charles Bailey <charles@hashpling.org> wrote:
> > I'll look at adding
> > a test case to mergetool and see how easy it is to get it to handle
> > this case better.
> 
> few weeks back I created a patch for mergetool, it was rejected
> ultimately on the basis that it had to cleanup temporary files and in
> reality this was a problem with a lot of mergetool, the suggestion was
> made that mergetool needs refactoring. I believe this problem is a
> similar symptom. basically mergetool should touch my files before I
> tell it what to do. if it has to move and back up my files before
> deciding then at the very least it should copy them back into place if
> I delete the remote. preferably in this case though it would just
> delete the remote or backup my local files and copy the remote in
> after I told it what to do (or maybe even delete my local files).

Coincidentally, last night I started looking at a mergetool
refactoring but more with unifying the handling of temporaries and
actions between the different types of merge (symlink, deleted file
and 'normal').

I'm more of the opinion that in any non-trivial case (i.e. not a
regular file/file merge), it *shouldn't* do anything until you tell it
what you want it to do. Clearly, between a tree and a blob, mergetool
is not going to be able to invoke a mergetool on set of three blobs,
but it should work out what it can do before prompting for a choice
from the user of what they want it to do.

-- 
Charles Bailey
http://ccgi.hashpling.plus.com/blog/

      reply	other threads:[~2009-02-24  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  6:04 how do I resolve this merge manually + mergetool bug Caleb Cushing
2009-02-24  6:31 ` Junio C Hamano
2009-02-24  6:52   ` Caleb Cushing
2009-02-24  7:16     ` Junio C Hamano
2009-02-24  7:19       ` Caleb Cushing
2009-02-24  7:47 ` Charles Bailey
2009-02-24  8:32   ` Caleb Cushing
2009-02-24  9:13     ` Charles Bailey [this message]

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=20090224091330.GB23927@hashpling.org \
    --to=charles@hashpling.org \
    --cc=git@vger.kernel.org \
    --cc=xenoterracide@gmail.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).