From: Johannes Sixt <j.sixt@viscovery.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Avoid invoking diff drivers during git-stash
Date: Fri, 19 Oct 2007 08:08:23 +0200 [thread overview]
Message-ID: <471849D7.1020303@viscovery.net> (raw)
In-Reply-To: <20071019013350.GA14020@spearce.org>
Shawn,
thanks for the fast response with a patch.
Shawn O. Pearce schrieb:
> Johannes Sixt <j.sixt@viscovery.net> wrote:
> > (1) Looking at git-stash.sh I see a few uses of 'git diff' in
> > apply_stash(). Shouldn't these use one of git-diff-{tree,index,files)? The
> > reason is that porcelain 'git diff' invokes custom diff drivers (that in my
> > case run a UI program), whereas the plumbing does not.
> >
> > Is there a particular reason to use porcelain 'git diff'?
>
> Does this fix the problem?
It does!
> @@ -110,7 +110,7 @@ show_stash () {
>
> w_commit=$(git rev-parse --verify "$s") &&
> b_commit=$(git rev-parse --verify "$s^") &&
> - git diff $flags $b_commit $w_commit
> + git diff-tree $flags $b_commit $w_commit
However, this porcelain 'git diff' should actually remain because it's part
of show_stash().
-- Hannes
next prev parent reply other threads:[~2007-10-19 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:32 git stash apply usability issues Johannes Sixt
2007-10-18 14:12 ` Steven Grimm
2007-10-19 1:31 ` Shawn O. Pearce
2007-10-19 13:27 ` Karl Hasselström
2007-10-19 13:57 ` David Kastrup
2007-10-19 1:33 ` [PATCH] Avoid invoking diff drivers during git-stash Shawn O. Pearce
2007-10-19 6:08 ` Johannes Sixt [this message]
2007-10-19 6:13 ` Shawn O. Pearce
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=471849D7.1020303@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).