Re: [RFC/PATCH 0/7] Rework git core for native submodules

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Apr 7, 2013, 21:11 UTC
Message-ID: <CALkWK0=GtOae9sizcftgCoqnoAOuQdGVQrcr2tKf7OCLDgMVSg@mail.gmail.com>
In-Reply-To: <20130407210225.GL2222@serenity.lan>

John Keeping wrote:

Show 7 quoted lines

> I do.  I quite often use "git add -p" to sort things out and submodules
> currently fit into that seamlessly: I can add the submodule and then
> wait until later to commit it, without needing to either clone and
> remember to "submodule add" later or commit and play with rebase.
>
> Losing the ability to do that is a major usability regression as far as
> I'm concerned.

I didn't realize people cared so deeply about this. Sure, we can emulate it: keeping the information in .git/link-specs/ doesn't sound like a bad idea. While it may feel like a hack, I think it's the right approach if we want to support non-fs-backed objects in our tree.

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