From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Any way to get complete diff up to a tag?
Date: Thu, 6 May 2010 17:27:17 +0200 [thread overview]
Message-ID: <20100506152717.GA12230@atjola.homenet> (raw)
In-Reply-To: <A612847CFE53224C91B23E3A5B48BAC74482E50F03@xmail3.se.axis.com>
On 2010.05.06 17:09:57 +0200, Peter Kjellerstedt wrote:
>
> Well, I figured out my mistake. I had abbreviated the SHA1 since I
> typed it in manually, and it worked fine in git's own repository,
> but not in another repository. But when I used the full SHA1 it
> worked in both. So I guess the empty dir SHA1 hardcoded in git just
> happened to be the SHA1 for the empty dir in git's own repository...
No, there can be only one SHA1 for the empty tree. It's the SHA1 hash of
the object, and the empty tree is the empty tree, always.
git.git just happens to actually contain that object, so the abbreviated
hash works, because git can find the object and doesn't actually need
the hardcoded built-in empty tree (which is only used when the full hash
is given).
Björn
next prev parent reply other threads:[~2010-05-06 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 9:27 Any way to get complete diff up to a tag? Peter Kjellerstedt
2010-05-06 9:42 ` Bert Wesarg
2010-05-06 9:42 ` Björn Steinbrink
2010-05-06 11:20 ` Peter Kjellerstedt
2010-05-06 13:00 ` Santi Béjar
2010-05-06 13:03 ` Johannes Sixt
2010-05-06 15:09 ` Peter Kjellerstedt
2010-05-06 15:27 ` Björn Steinbrink [this message]
2010-05-06 17:08 ` Linus Torvalds
2010-05-06 18:38 ` Greg Troxel
2010-05-07 16:35 ` Peter Kjellerstedt
2010-05-06 15:43 ` Knittl
2010-05-07 4:17 ` Peter Kjellerstedt
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=20100506152717.GA12230@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=peter.kjellerstedt@axis.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