Re: [RFC/PATCH 0/7] Rework git core for native submodules
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Apr 17, 2013, 12:14 UTC
- Message-ID
- <CALkWK0mp5H2hXXBX6YDMSto+DHjXsAojQDb3vcJksUwoOV=2jg@mail.gmail.com>
- In-Reply-To
- <CACsJy8Bw6x=WiQUi0C4ZtEQiA9ia8ZFgz5uH61K6kf-JPy1xyg@mail.gmail.com>
Duy Nguyen wrote:
Show 11 quoted lines
> On Wed, Apr 17, 2013 at 9:56 PM, Ramkumar Ramachandra > <artagnon@gmail.com> wrote: >>> 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.
Oh, I interpreted your typo "nea" as "neat", when you meant "new". Yeah, it's worth exploring: I don't know what backward compatibility benefits it will yield yet.