git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Deon George <deon.george@gmail.com>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org
Subject: Re: Feature Enhancement Idea.
Date: Wed, 23 Sep 2009 21:12:47 +1000	[thread overview]
Message-ID: <5b5e291e0909230412r3ce143abgd990c36e27736bae@mail.gmail.com> (raw)
In-Reply-To: <200909231106.03305.johan@herland.net>

2009/9/23 Johan Herland <johan@herland.net>:
> Have a look at git submodules ('git help submodule'), or the git-subtree
> script that has been discussed on this list a couple of times [1].

git submodule looks like it will do a little of what I want - I'll do
some more reading on it to see exactly how it works. Thanks for the
tip.

My initial look at it seems to miss an important feature that my layer
idea would provide. It looks like git submodule assumes that
everything in a subdirectory belongs to a repository - with my layer
idea, I would want any layer to share the same directory structure and
files (or content) belonging to a distinct layer's repository.

IE:
the base might provide
plugins
plugins/README
modules
modules/README
lib/common.php

and a layer might provide
plugins/a.php
modules/a.php
lib/a.php

another layer might provide
plugins/b.php
modules/b.php
lib/b.php

If I was a C developer, I'd have a go at creating it - but I'm just a
php developer :)
...deon

  reply	other threads:[~2009-09-23 11:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  6:17 Feature Enhancement Idea Deon George
2009-09-23  8:26 ` Christian Couder
2009-09-23  9:06 ` Johan Herland
2009-09-23 11:12   ` Deon George [this message]
2009-09-23 18:17     ` Ciprian Dorin, Craciun
2009-09-23 23:19       ` Johan Herland
2009-09-23 20:08 ` Junio C Hamano
2009-09-24  5:52   ` Deon George
2009-09-24  5:56 ` Jakub Narebski
2009-09-24  9:25   ` Deon George
2009-09-24 16:45     ` Eric Raible

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=5b5e291e0909230412r3ce143abgd990c36e27736bae@mail.gmail.com \
    --to=deon.george@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.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 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).