From: Jeff King <peff@peff.net>
To: Andy Lowry <andy.work@nglowry.com>
Cc: git <git@vger.kernel.org>
Subject: Re: BUG in git diff-index
Date: Thu, 31 Mar 2016 10:27:04 -0400 [thread overview]
Message-ID: <20160331142704.GC31116@sigill.intra.peff.net> (raw)
In-Reply-To: <CAJxkE8SVF_ikHqDCh6eHExq=seitHPVpxW2GmPo40jtqWvz1JQ@mail.gmail.com>
On Thu, Mar 31, 2016 at 10:12:07AM -0400, Andy Lowry wrote:
> What I'm actually after is a tree-to-filesystem comparison, regardless
> of index. I've currently got a "diff" thrown in as a "work-around"
> before "diff-index", but now I understand it's not a workaround at
> all. If there's a better way to achieve what I'm after, I'd appreciate
> a tip. Otherwise I'll just change the comments explaining why there's
> a "diff" in my script.
If your workaround is just to refresh the index, then you can do "git
update-index --refresh", rather than diff.
I don't think there is a plumbing command to do a direct
filesystem-to-tree comparison without having an index at all. "git diff
<treeish>" claims in the documentation to do so, but besides not being
plumbing, I think it is really just doing the same thing as diff-index,
under the hood. The index is a pretty fundamental part of git's view of
the working tree.
-Peff
next prev parent reply other threads:[~2016-03-31 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 12:39 BUG in git diff-index Andy Lowry
2016-03-31 13:57 ` Carlos Martín Nieto
2016-03-31 14:05 ` Jeff King
2016-03-31 14:12 ` Andy Lowry
2016-03-31 14:27 ` Jeff King [this message]
2016-03-31 19:30 ` Andy Lowry
2016-03-31 20:39 ` Junio C Hamano
2017-09-26 19:46 ` Marc Herbert
2017-09-26 20:11 ` Eric Wong
2017-09-26 23:27 ` Google indexing https://public-inbox.org/git (was: BUG in git diff-index) Marc Herbert
2017-09-27 21:06 ` Wrong -dirty suffix set by setlocalversion " Marc Herbert
2018-05-24 23:03 ` Mike Mason
2018-05-25 3:50 ` Marc Herbert
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160331142704.GC31116@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andy.work@nglowry.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).