From: "H. Peter Anvin" <hpa@zytor.com>
To: "David A. Wheeler" <dwheeler@dwheeler.com>
Cc: Petr Baudis <pasky@ucw.cz>, Pavel Roskin <proski@gnu.org>,
git <git@vger.kernel.org>,
Joel.Becker@oracle.com
Subject: Re: commit-id fails after cg-init
Date: Wed, 04 May 2005 08:45:36 -0700 [thread overview]
Message-ID: <4278EE20.8080004@zytor.com> (raw)
In-Reply-To: <4278E6D4.6060807@dwheeler.com>
David A. Wheeler wrote:
> Joel Becker said:
>
>> Well, cg-init in this case creates no objects. I'd say,
>> instead, it should create an empty tree object (representing a project
>> with no files) and commit that. That would be your initial commit, and
>> would put something valid in heads/master.
>
> That would actually make sense; commits would go all the way
> back to the "empty tree" as the ultimate initial tree.
>
> There's an interesting side-effect of this; I _think_ it's
> fine but it might be worth thinking through. If all
> new projects start with an empty tree, that creates a
> "common root" that all projects can appeal to.
> That means that in theory a merge between any two project root
> trees can eventually find a common ancestor: the empty tree.
> I _think_ that's okay... is it?
>
In fact, I think that's a Very Good Thing... it eliminates an
unnecessary corner case. Same reason linked lists want head nodes and
all that jazz.
-hpa
next prev parent reply other threads:[~2005-05-04 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 20:03 commit-id fails after cg-init Pavel Roskin
2005-05-03 21:13 ` Petr Baudis
2005-05-04 15:14 ` David A. Wheeler
2005-05-04 15:45 ` H. Peter Anvin [this message]
2005-05-05 7:22 ` Alexey Nezhdanov
2005-05-06 3:06 ` David A. Wheeler
2005-05-03 21:14 ` Joel Becker
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=4278EE20.8080004@zytor.com \
--to=hpa@zytor.com \
--cc=Joel.Becker@oracle.com \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=proski@gnu.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).