From: Jeff King <peff@peff.net>
To: Philip Oakley <philipoakley@iee.org>
Cc: Hilco Wijbenga <hilco.wijbenga@gmail.com>,
Git Users <git@vger.kernel.org>
Subject: Re: Rebase & Trailing Whitespace
Date: Thu, 1 Sep 2011 17:26:18 -0400 [thread overview]
Message-ID: <20110901212618.GB16308@sigill.intra.peff.net> (raw)
In-Reply-To: <29267EE41F9343E68AAAE2C33AA40E1A@PhilipOakley>
On Thu, Sep 01, 2011 at 10:00:38PM +0100, Philip Oakley wrote:
> >[1] If you don't remember the empty tree sha1, you can always derive it
> > with:
> >
> > git hash-object -t tree /dev/null
> >
>
> I've added this tip to the
> https://git.wiki.kernel.org/index.php/Aliases page
Thanks. By itself, I think many readers would ask "why would I want the
empty tree, so I threw in a few examples of use on the wiki, too.
-Peff
next prev parent reply other threads:[~2011-09-01 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 23:55 Rebase & Trailing Whitespace Hilco Wijbenga
2011-09-01 2:31 ` Jeff King
2011-09-01 21:00 ` Philip Oakley
2011-09-01 21:26 ` Jeff King [this message]
2011-09-02 7:32 ` Michael J Gruber
2011-09-02 8:28 ` Jeff King
2011-09-03 20:18 ` Clemens Buchacher
2011-09-09 19:38 ` 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=20110901212618.GB16308@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=hilco.wijbenga@gmail.com \
--cc=philipoakley@iee.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).