From: Johannes Gilger <heipei@hackvalue.de>
To: git@vger.kernel.org
Subject: diff-index --cached on bare repository
Date: Fri, 30 Jan 2009 16:13:53 +0000 (UTC) [thread overview]
Message-ID: <glv901$c5v$1@ger.gmane.org> (raw)
Hi list,
today I stumbled over the output of "git diff-index --cached HEAD" in a
bare repository. While diff-index HEAD just reminds me that I got to
have a work-tree, --cached outputs all the files in HEAD as deleted. The
question is if this is intended behaviour? Or is it irrelevant because
diff-index is only plumbing? I found a mail of the gitk-team working
around this, which is funny because I discovered this while working on
GitX.
So please, enlighten me ;)
Greetings,
Jojo
--
Johannes Gilger <heipei@hackvalue.de>
http://hackvalue.de/heipei/
GPG-Key: 0x42F6DE81
GPG-Fingerprint: BB49 F967 775E BB52 3A81 882C 58EE B178 42F6 DE81
next reply other threads:[~2009-01-30 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 16:13 Johannes Gilger [this message]
2009-01-30 20:06 ` diff-index --cached on bare repository 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='glv901$c5v$1@ger.gmane.org' \
--to=heipei@hackvalue.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).