From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"Rhodes, Kate" <masukomi@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] add--interactive: handle initial commit better
Date: Wed, 13 Feb 2008 08:15:23 -0500 [thread overview]
Message-ID: <20080213131523.GA3266@coredump.intra.peff.net> (raw)
In-Reply-To: <m3fxvxc87u.fsf@localhost.localdomain>
On Wed, Feb 13, 2008 at 05:11:10AM -0800, Jakub Narebski wrote:
> > Heh. This is cute. But it is also a bit hard to reference, no? I mean,
> > you have to remember the SHA-1 of it...
> >
> > Maybe {} ?
>
> Or NULL? You can do this even without modifying git code, I think, by
> adding refs/NULL with appropriate sha-1...
You still need my patch, unless you want to create the empty tree object
in the databsae. The existence of the object and its name are separate.
If you want to add a magic ref or syntax that maps to the correct SHA-1,
then that makes sense to me.
-Peff
next prev parent reply other threads:[~2008-02-13 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 0:59 [Bug] git add -i fails in multiple ways prior to first commit Rhodes, Kate
2008-02-13 10:16 ` Jeff King
2008-02-13 10:23 ` Jakub Narebski
2008-02-13 10:37 ` Jeff King
2008-02-13 10:50 ` [PATCH] add--interactive: handle initial commit better Jeff King
2008-02-13 11:25 ` Jeff King
2008-02-13 12:19 ` Johannes Schindelin
2008-02-13 13:11 ` Jakub Narebski
2008-02-13 13:15 ` Jeff King [this message]
2008-02-13 13:22 ` Johannes Schindelin
2008-02-13 13:45 ` Johannes Schindelin
2008-02-13 11:30 ` [Bug] git add -i fails in multiple ways prior to first commit Junio C Hamano
2008-02-13 11:34 ` 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=20080213131523.GA3266@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=masukomi@gmail.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;
as well as URLs for NNTP newsgroup(s).