From: David Aguilar <davvid@gmail.com>
To: Marcin Zalewski <marcin.zalewski@gmail.com>
Cc: markus.heidelberg@web.de, git@vger.kernel.org
Subject: Re: Diftool problems
Date: Sat, 2 May 2009 02:05:33 -0700 [thread overview]
Message-ID: <20090502090531.GC34467@gmail.com> (raw)
In-Reply-To: <7c0fdf4f0904291255i4076df8cubb26fdb2d51826d4@mail.gmail.com>
On 0, Marcin Zalewski <marcin.zalewski@gmail.com> wrote:
> > The real fix would be to adjust the ediff snippet for difftool support.
>
> "$merge_tool_path" -f emerge-files-command \
> "$LOCAL" "$REMOTE" "$(basename "$MERGED")"
Hi
Would the right command be:
"$merge_tool_path" -f emerge-files-command \
"$LOCAL" "$REMOTE"
(without $MERGED) ?
> I think that merge result could be a temporary file, like in
> mergetool. In a situation where I use git to track an SVN repository,
> difftool can be actually used to merge my uncommitted changes with a
> commit from someone else after doing svn rebase. On the other hand, I
> am no git expert so there may be a better way to handle this case.
>
> -m
Are you able to save the result to a file with the above
snippet? I'd prefer to not touch the way difftool deals
with files this late in the RC cycle, and if just
saving within emacs works without changing difftool
to use temporary files then that's even better.
I tried it and didn't notice any difference w/ or w/out
the patch, but if not specifying $MERGED is more
correct then we should do that.
You should have just seen a patch from me.
Let me know if you have any other suggestions.
--
David
prev parent reply other threads:[~2009-05-02 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 16:15 Diftool problems Marcin Zalewski
2009-04-29 19:42 ` Markus Heidelberg
2009-04-29 19:55 ` Marcin Zalewski
2009-04-29 20:48 ` Markus Heidelberg
2009-04-29 21:37 ` Marcin Zalewski
2009-05-02 9:05 ` David Aguilar [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=20090502090531.GC34467@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=marcin.zalewski@gmail.com \
--cc=markus.heidelberg@web.de \
/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).