From: Nick Edelen <sirnot@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nicolas Pitre <nico@cam.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sam Vilain <sam@vilain.net>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 1/6 (v2)] revision caching documentation: man page and technical discussion
Date: Sun, 9 Aug 2009 16:01:22 +0200 [thread overview]
Message-ID: <c77435a80908090701x3aa2584fq353df1886ed1b02@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2009-08-09 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 7:31 [PATCH 1/6 (v2)] revision caching documentation: man page and technical discussion Nick Edelen
2009-08-08 18:31 ` Junio C Hamano
2009-08-09 14:01 ` Nick Edelen [this message]
2009-08-09 18:16 ` Junio C Hamano
2009-08-16 22:41 ` Nick Edelen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c77435a80908090701x3aa2584fq353df1886ed1b02@mail.gmail.com \
--to=sirnot@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@couder.net \
--cc=exon@op5.se \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).