From: Jeff King <peff@peff.net>
To: Eric Frederich <eric.frederich@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Get a git diff without taking index into account
Date: Wed, 18 Feb 2015 13:32:51 -0500 [thread overview]
Message-ID: <20150218183251.GB6346@peff.net> (raw)
In-Reply-To: <CAAoZyYOst-5cD7qtV=T3Oahja1JN1ZmeyAcELrn7xD0bMc7Mrg@mail.gmail.com>
On Wed, Feb 18, 2015 at 01:27:50PM -0500, Eric Frederich wrote:
> My immediate concern is not to fix the documentation but to get some
> sort of status or diff.
> I want to avoid using an index because I want to allow multiple
> processes to do different diffs at the same time.
If you only have one working tree, can't all of the processes use the
same index (that matches the working tree) and do different diffs
against it?
If you have multiple working trees, can you use one index per working
tree, and specify it using GIT_INDEX_FILE?
If you can persist the index file for each working tree, this will be
much faster in the long run, too (you can just refresh the index before
each diff, which means that git does not have to actually open the files
in most cases; we can compare their stat information to what is in the
index, and then the index sha1 with what is in the tree).
-Peff
next prev parent reply other threads:[~2015-02-18 18:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 14:57 Get a git diff without taking index into account Eric Frederich
2015-02-18 15:06 ` Eric Frederich
2015-02-18 15:37 ` Junio C Hamano
2015-02-18 15:42 ` Eric Frederich
2015-02-18 16:33 ` Junio C Hamano
2015-02-18 18:27 ` Eric Frederich
2015-02-18 18:32 ` Jeff King [this message]
2015-02-18 19:36 ` Eric Frederich
2015-02-18 21:38 ` Eric Frederich
2015-02-18 22:16 ` Junio C Hamano
2015-02-18 22:30 ` Jeff King
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=20150218183251.GB6346@peff.net \
--to=peff@peff.net \
--cc=eric.frederich@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).