From: Tim Henigan <tim.henigan@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org, Alex Riesen <raa.lkml@gmail.com>
Subject: Re: [PATCH 6/9] difftool: replace system call with Git::command_noisy
Date: Sat, 17 Mar 2012 21:21:47 -0400 [thread overview]
Message-ID: <CAFouetgJsHD9UoVPE6V16vAsJ4Q1neHzH7jrwGma6e2ZHELgFA@mail.gmail.com> (raw)
In-Reply-To: <CAJDDKr4+0iWoZhxo6kMVa0YUtDzmrH=XTZnDqQdbnM6TJ41UDg@mail.gmail.com>
On Fri, Mar 16, 2012 at 10:48 PM, David Aguilar <davvid@gmail.com> wrote:
> On Fri, Mar 16, 2012 at 6:59 PM, Tim Henigan <tim.henigan@gmail.com> wrote:
>
> In general, I am a little nervous about having difftool copy worktree
> content somewhere temporary only to copy it back in later. Is there
> some way to make the diff machinery reuse the worktree? I was under
> the impression that we could do some GIT_INDEX tricks to do it, though
> I will admit that I did not read that suggestion in depth, nor did I
> grasp whether this was the problem it was meant to address.
I have not been able to find any other way to do it. The GIT_INDEX
trick allows the tmp directories to be built using 'git update-index'
and 'git checkout-index', but they offer no help for this problem.
If we use the working tree directory as one of the diff targets, then
all the files in the working directory would be included in the
diff...unless there was some way to remove the files that aren't part
of the diff from the working tree. However at that point, I don't
think the solution would be any better (i.e. deleting files from the
working tree and then checking them back out is no better than copying
files to the tmp dir and back again).
The only other option I can think of is to build a complete copy of
the repo in the tmp directory for comparison against the working tree.
However, this could obviously lead to resource/performance problems
on large repos.
I am open to suggestions, but I have not found any better solution.
prev parent reply other threads:[~2012-03-18 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 1:59 [PATCH 6/9] difftool: replace system call with Git::command_noisy Tim Henigan
2012-03-17 2:48 ` David Aguilar
2012-03-17 10:50 ` Alex Riesen
2012-03-17 14:48 ` Tim Henigan
2012-03-17 19:54 ` Alex Riesen
2012-03-18 1:21 ` Tim Henigan [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=CAFouetgJsHD9UoVPE6V16vAsJ4Q1neHzH7jrwGma6e2ZHELgFA@mail.gmail.com \
--to=tim.henigan@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=raa.lkml@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).