From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 6/9] Use uint32_t for pack-objects counters.
Date: Wed, 07 Mar 2007 13:52:09 -0800 [thread overview]
Message-ID: <7vodn4en7a.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070307203721.GD27922@spearce.org> (Shawn O. Pearce's message of "Wed, 7 Mar 2007 15:37:21 -0500")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Its always scanned backwards. I've read the patch like 8 times
> now (and I just reread the part you quoted). The patch implements
> the same backwards scan that has always been there.
Sorry, false alarm. Yes we scanned from larger to smaller and
you still do.
prev parent reply other threads:[~2007-03-07 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 1:44 [PATCH 6/9] Use uint32_t for pack-objects counters Shawn O. Pearce
2007-03-07 19:02 ` Junio C Hamano
2007-03-07 20:37 ` Shawn O. Pearce
2007-03-07 21:52 ` Junio C Hamano [this message]
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=7vodn4en7a.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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