git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Feature Enhancement Idea.

From
Christian Couder <christian.couder@gmail.com>
Date
Sep 23, 2009, 08:26 UTC
Message-ID
<c07716ae0909230126w36b3309fqe9ae8ccec0db49c3@mail.gmail.com>
In-Reply-To
<5b5e291e0909222317q47ae36d4la470f17ec3902124@mail.gmail.com>
Hi,
On Wed, Sep 23, 2009 at 8:17 AM, Deon George <deon.george@gmail.com> wrote:
Show 16 quoted lines
> 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.

Previous: Deon GeorgeNext: Johan Herland
Message 2 of 11 in “Feature Enhancement Idea.”
  1. Deon GeorgeSep 23, 2009
  2. Christian CouderSep 23, 2009
  3. Johan HerlandSep 23, 2009
  4. Deon GeorgeSep 23, 2009
  5. Ciprian Dorin, CraciunSep 23, 2009
  6. Johan HerlandSep 23, 2009
  7. Junio C HamanoSep 23, 2009
  8. Deon GeorgeSep 24, 2009
  9. Jakub NarebskiSep 24, 2009
  10. Deon GeorgeSep 24, 2009
  11. Eric RaibleSep 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.