From: Christian Couder <christian.couder@gmail.com>
To: Deon George <deon.george@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Feature Enhancement Idea.
Date: Wed, 23 Sep 2009 10:26:49 +0200 [thread overview]
Message-ID: <c07716ae0909230126w36b3309fqe9ae8ccec0db49c3@mail.gmail.com> (raw)
In-Reply-To: <5b5e291e0909222317q47ae36d4la470f17ec3902124@mail.gmail.com>
Hi,
On Wed, Sep 23, 2009 at 8:17 AM, Deon George <deon.george@gmail.com> wrote:
> Hi,
>
> I'm not sure if this is the right place, but I thought I'd post my
> idea and maybe somebody will either redirect me to the right place, or
> give me that "that wont happen".
>
> Im fairly new to GIT (wish I had discovered it long ago), and I really
> like using it - great work guys/garls :)
>
> My idea is to enhance GIT to support (I'll call it) development
> "layers". The current design of GIT is that the working repository and
> working directory assume that all files belong together in the same
> project. I would like to see GIT go 3D and support layers, so that
> files (and/or file content) can belong to multiple repositories (or
> considered unique projects), even though the working tree presents all
> files as if they were one.
Perhaps you could have a look at "git replace" that is now in the master branch.
It could be improved to provide different "views" of a single repository.
I don't think that alone it would provide everything you want though.
Best regards,
Christian.
next prev parent reply other threads:[~2009-09-23 8:27 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 [this message]
2009-09-23 9:06 ` Johan Herland
2009-09-23 11:12 ` Deon George
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=c07716ae0909230126w36b3309fqe9ae8ccec0db49c3@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=deon.george@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 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).