git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/6 (v2)] revision caching documentation: man page and technical discussion

From
NENick Edelen <sirnot@gmail.com>
Date
Aug 9, 2009, 14:01 UTC
Message-ID
<c77435a80908090701x3aa2584fq353df1886ed1b02@mail.gmail.com>
In-Reply-To
<7vbpmqi2d4.fsf@alter.siamese.dyndns.org>
Wow, thank you very much for your commentary!

Unfortunately I don't have a stable internet connection this week (although I can get on at minimum once a day), but I'll rework the docs today and upload a new patch for them tomorrow or the next day. I'll also fix the file permissions ;-)

As you said, I'll answer most of your questions in the revised docs, but I have one question about the time field size. git uses unsigned long internally for its commit date, so it'd be limited by the 32bits a long is on 32bit archs. So, wouldn't the commit times effectively be a uin32_t? I mean if not I can change it; I just figured I'd save some space.

Other than that there shouldn't be an overflow problem, unless someone's merging over 63 branches in one go. Maybe I'll expand that a bit just in case though...

Thanks again,
 - Nick
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 5 in “revision caching documentation: man page and technical discussion”
  1. 1/6 revision caching documentation: man page and technical discussionNick Edelen, Aug 8, 2009
  2. Junio C HamanoAug 8, 2009
  3. Nick EdelenAug 9, 2009
  4. Junio C HamanoAug 9, 2009
  5. Nick EdelenAug 16, 2009

Read the whole thread, see it on lore, or plain text.

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