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

From: Duy Nguyen <pclouds@gmail.com>
Date: Apr 17, 2013, 12:06 UTC
Message-ID: <CACsJy8Bw6x=WiQUi0C4ZtEQiA9ia8ZFgz5uH61K6kf-JPy1xyg@mail.gmail.com>
In-Reply-To: <CALkWK0m9QmZaSDruY=+2F-Kkw+fd6E1TYCTBpVQHRJrzq2VjCQ@mail.gmail.com>

On Wed, Apr 17, 2013 at 9:56 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 5 quoted lines

>> why not reuse tag object with some nea header lines?
>
> Or a unified blob, which is currently what we have.  The point is to
> have structured parseable information that the object-parsing code of
> git code and easily slurp and give to the rest of git-core.

I think you misunderstood. I meant instead of introducing new object type OBJ_LINK, you can reuse tag object and add new header lines for your purposes.

> Please clear your reading backlog to avoid bringing up the same points
> over and over again.

Yep. I'll shut up until it's cleared. -- Duy

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