All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Bartoschek <bartoschek@gmx.de>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Submodules implementation
Date: Wed, 24 Feb 2010 01:15:53 +0100	[thread overview]
Message-ID: <201002240115.53771.bartoschek@gmx.de> (raw)
In-Reply-To: <32541b131002231559r49fc31e0i4ce46869d27190c8@mail.gmail.com>

Am Mittwoch 24 Februar 2010 schrieb Avery Pennarun:

> The data format itself implements submodules as simply pointers to
> commits (not trees) located at a particular point in the supermodule.
> This is very elegant and simple.

I see that in the submodule there is a .git directory with its own objects.  
This does not look like as if the submodule objects are part of the 
superproject.

> By comparison, my git-subtree tool
> (http://github.com/apenwarr/git-subtree) is the opposite: its data
> storage format isn't very elegant (it just has a tree stored inside
> another tree, as if there were no submodule at all) but its
> implementation makes it easier for end users (since they don't have to
> deal with separate repositories).

This is exaclty how I would expect it. The tree of the submodule has its root 
somewhere in the tree of the superproject. Then there are commits for the 
superproject that point to the root of the whole tree and commits for the 
submodules that point to nodes in the tree.
A combined tree looks much more elegant for me.

I'll take a look at your tool.

Christop

  reply	other threads:[~2010-02-24  0:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 23:50 Submodules implementation Christoph Bartoschek
2010-02-23 23:59 ` Avery Pennarun
2010-02-24  0:15   ` Christoph Bartoschek [this message]
2010-02-24  0:40     ` Junio C Hamano

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=201002240115.53771.bartoschek@gmx.de \
    --to=bartoschek@gmx.de \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.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 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.