All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Any way to get complete diff up to a tag?
Date: Thu, 06 May 2010 15:03:40 +0200	[thread overview]
Message-ID: <4BE2BE2C.8050403@viscovery.net> (raw)
In-Reply-To: <A612847CFE53224C91B23E3A5B48BAC74482E50DE7@xmail3.se.axis.com>

Am 5/6/2010 13:20, schrieb Peter Kjellerstedt:
> Björn Steinbrink
>> git internally knows about the empty tree, so you can use:
>> git diff 4b825dc642cb6eb9a060e54bf8d69288fbee4904 v1.7.1
>>
>> Björn
> 
> Thank you, that was useful. However, I need to be able to do this
> for an arbitrary repository, and that SHA seems to be specific for 
> the git repository. How do I get the SHA for the empty tree in an 
> arbitrary repository?

Aha, so you think Björn et.al. were able to guess the SHA1 for your
specific repository? ;)

No, the empty tree is the empty tree, and its name is as cited above, no
matter where in the universe you are.

-- Hannes

  parent reply	other threads:[~2010-05-06 13:03 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 [this message]
2010-05-06 15:09       ` Peter Kjellerstedt
2010-05-06 15:27         ` Björn Steinbrink
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=4BE2BE2C.8050403@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=B.Steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --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 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.