Re: [PATCH 1/6 (v2)] revision caching documentation: man page and technical discussion
- From
- Nick 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