From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
To: git@vger.kernel.org
Subject: Re: tool to diff cache <-> working directory
Date: Fri, 6 May 2005 04:07:59 +0200 [thread overview]
Message-ID: <20050506020759.GA11506@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <7vhdhhf88u.fsf@assigned-by-dhcp.cox.net>
Hello,
> git-diff-tree tree1 tree2 two trees
> git-diff-cache --cached tree1 cache and tree
> git-diff-cache tree1 tree and working directory
> git-diff-files cache and working directory
that makes it clear. Thanks.
> So git-diff-files is not just similar to but exactly is what you
> want if I read your question correctly.
Yes, it is. :-)
> Yes there is a way, git-write-blob, but why would you want to do
> that?
I thought there would be no cache<->working directory delta generation.
And I need a way to see if there are unchecked-in deltas in the working
tree. So I thought about looking at the 'git-diff-cache --cached tree1'
and comparing it with the self generated SHAs of the working tree. But
now, that there is such a tool, I am perfectly fine.
Thanks,
Thomas
next prev parent reply other threads:[~2005-05-06 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 0:23 tool to diff cache <-> working directory Thomas Glanzmann
2005-05-06 1:33 ` Junio C Hamano
2005-05-06 2:07 ` Thomas Glanzmann [this message]
2005-05-06 2:48 ` Junio C Hamano
2005-05-06 3:13 ` Thomas Glanzmann
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=20050506020759.GA11506@cip.informatik.uni-erlangen.de \
--to=sithglan@stud.uni-erlangen.de \
--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.
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).