Re: [RFC] Submodules in GIT

From: Torgil Svensson <torgil.svensson@gmail.com>
Date: Dec 4, 2006, 20:26 UTC
Message-ID: <e7bda7770612041226j4d4a5584m279afa9a2d7dfe74@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0612030946150.3476@woody.osdl.org>

On 12/3/06, Linus Torvalds <torvalds@osdl.org> wrote:

Show 8 quoted lines

>
> > If you have an old irrelevant submodule in the history that happens to
> > have the same name as one of them you are interested in, do you get
> > this as well?
>
> It could be "solved" by simply having the requirement that all modules
> need to be named differently (notice that "module name" is _not_ the same
> thing as "the directory name where the module shows up".

Okay, missed that part. I wasn't familiar with contents of the CVS modules files and misinterpreted your suggestion.

MODULE [OPTIONS] [&OTHERMODULE...] [DIR] [FILES]

So all this is UI only and the "normal" operations on the supermodule

$ 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.