From: Stefan Monnier <monnier@iro.umontreal.ca>
To: git@vger.kernel.org
Subject: Can't diff against the 00000000 revision
Date: Tue, 12 Jan 2016 10:17:24 -0500 [thread overview]
Message-ID: <jwv4meiygrc.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
If I look at the initial commit on a branch, I see something like:
% git show d59cfff346c3e210adc26501f8cebf8da5ab2e7d
commit d59cfff346c3e210adc26501f8cebf8da5ab2e7d
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Wed Dec 2 20:46:51 2015 -0500
Initial release
diff --git a/bugit b/bugit
new file mode 100755
index 0000000..681bd38
--- /dev/null
+++ b/bugit
@@ -0,0 +1,512 @@
...
which is great. But I can't get the same result with
git diff 0000000..681bd38
because it complains:
% git diff 0000000..681bd38
fatal: ambiguous argument '0000000..681bd38': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
%
I bumped into this problem in a post-receive hook where I need to pay
attention to all newly added files, and where this problem means that
I can't use the same code for a newly added branch as for a push on
a pre-existing branch.
I currently work around the problem by adding a dummy empty branch, but
being able to use the revision 00000000 as a known reference to an empty
tree would come in really handy, and since it's already used at various
places in Git (post-receive hook and "git show" output, at least), it
would seem like a natural extension.
Stefan
next reply other threads:[~2016-01-12 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 15:17 Stefan Monnier [this message]
2016-01-12 15:32 ` Can't diff against the 00000000 revision Jeff King
2016-01-12 15:37 ` Jeff King
2016-01-12 16:26 ` Stefan Monnier
2016-01-12 18:20 ` Jeff King
2016-01-12 18:52 ` Junio C Hamano
2016-01-12 18:11 ` Andreas Schwab
2016-01-12 18:21 ` 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=jwv4meiygrc.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.