From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Kate Rhodes <masukomi@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] hard-code the empty tree object
Date: Fri, 15 Feb 2008 09:11:56 -0800 [thread overview]
Message-ID: <7vabm2i1pf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080214103256.GA17951@coredump.intra.peff.net
Jeff King <peff@peff.net> writes:
> We also hard-code the special ref '{}' as an alias for the
> empty tree. Users may refer to the empty tree by its
> sha1 or by '{}'.
I think the users of hard coded empty tree are oddballs. Let's
not be too cute and instead leave it in the add -i patch. {} is
already too cute.
next prev parent reply other threads:[~2008-02-15 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 10:32 [PATCH 1/2] hard-code the empty tree object Jeff King
2008-02-14 12:39 ` Johannes Schindelin
2008-02-14 14:03 ` Jeff King
2008-02-15 17:11 ` Junio C Hamano [this message]
2008-02-15 17:20 ` Jeff King
2008-02-15 17:42 ` Junio C Hamano
2008-02-15 18:25 ` 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=7vabm2i1pf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=masukomi@gmail.com \
--cc=peff@peff.net \
/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).