All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, "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 05:11:10 -0800 (PST)	[thread overview]
Message-ID: <m3fxvxc87u.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.1.00.0802131213270.30505@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Wed, 13 Feb 2008, Jeff King wrote:
> >  	}
> > +	if (!hashcmp(sha1, empty_tree.sha1))
> > +		return &empty_tree;
> >  	return NULL;
> >  }
> 
> 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...

^{tree} I think resolves to HEAD^{tree}

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-02-13 13:11 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 [this message]
2008-02-13 13:15           ` Jeff King
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=m3fxvxc87u.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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.