Re: [StGit PATCH] Parse commit object header correctly
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Feb 10, 2012, 04:27 UTC
- Message-ID
- <CACsJy8AT68zYHnWGurVW19-SZMXoMYhagWqG7iQENBLU9qsRMA@mail.gmail.com>
- In-Reply-To
- <20120209175158.GA7384@burratino>
On Fri, Feb 10, 2012 at 12:51 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 7 quoted lines
> No. There is one list of supported headers, and this list is the > standards body that maintains it[*]. So if you end up needing an > extension to the commit object format, that can be done, but it needs > to be accepted here (and ideally checked by "git fsck", though it's > lagging a bit in that respect lately). > > [*] http://thread.gmane.org/gmane.comp.version-control.git/138848/focus=138892
Doesn't this deserve a document in Documentation/technical? It's also a good opportunity to document tree and tag object format in addition to commit object. I did not check thoroughly but the commit that introduced encoding field, 4b2bced, did not come with any document updates, so I assume it has not been documented ever since.
-- Duy