From: Kay Sievers <kay.sievers@vrfy.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: hmm, can't we give the "root" a parent?
Date: Mon, 12 Sep 2005 21:59:47 +0200 [thread overview]
Message-ID: <20050912195947.GA28502@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509121123280.3242@g5.osdl.org>
On Mon, Sep 12, 2005 at 11:26:24AM -0700, Linus Torvalds wrote:
> On Mon, 12 Sep 2005, Kay Sievers wrote:
> >
> > Can't we teach the git tools that a "root commit" (one without a any
> > parent) is not visible as a "root", if let's say:
> > .git/parents/<root-commit-id> -> <fake-parent-id>
> >
> > does connect a "fake" parent to the "root"? This way we could add any
> > older Linux history to the current tree. Combined with "alternates" it
> > could live in a complete different repository too.
>
> Ehh.. That's exactly what "grafting" is about.
>
> So just do
>
> echo "<root-id> <grafted-parent-id>" >> .git/info/grafts
>
> and it should all work.
>
> Of course, anything that parses the commits by hand won't see it, but all
> the regular tools hopefully do.
Yup, tried it and works nicely with the history.git tree on kernel.org
connected to your tree, replacing the initial commit.
And good to know about that, need to fix the "parent" link in gitweb to
respect grafts.
Thanks,
Kay
next prev parent reply other threads:[~2005-09-12 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 18:11 hmm, can't we give the "root" a parent? Kay Sievers
2005-09-12 18:26 ` Linus Torvalds
2005-09-12 19:59 ` Kay Sievers [this message]
2005-09-12 20:21 ` Linus Torvalds
2005-09-12 21:00 ` Kay Sievers
2005-09-12 21:42 ` Linus Torvalds
2005-09-12 22:50 ` Kay Sievers
2005-09-12 23:06 ` Linus Torvalds
2005-09-12 23:09 ` Linus Torvalds
2005-09-12 23:51 ` Kay Sievers
2005-09-12 18:27 ` A Large Angry SCM
2005-09-16 15:39 ` gitweb search in multi-headed tree Tony Luck
2005-09-17 1:22 ` Kay Sievers
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=20050912195947.GA28502@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).