From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 11/10] allow forcing index v2 and 64-bit offset treshold
Date: Mon, 09 Apr 2007 17:23:24 -0700 [thread overview]
Message-ID: <7vejmtxekj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0704091901290.28181@xanadu.home> (Nicolas Pitre's message of "Mon, 09 Apr 2007 19:04:52 -0400 (EDT)")
Nicolas Pitre <nico@cam.org> writes:
> On Mon, 9 Apr 2007, Junio C Hamano wrote:
>
>> Nicolas Pitre <nico@cam.org> writes:
>>
>> > This is necessary for testing the new capabilities in some automated
>> > way without having an actual 4GB+ pack.
>> >
>> > Signed-off-by: Nicolas Pitre <nico@cam.org>
>> > ---
>> >
>> > I should write some tests... when I have more time.
>>
>> It appears everybody is short of time. I am having two
>> troubles. Nobody seems to have positive nor negative reports or
>> comments on what are cooking in 'next' so nothing can graduate,
>> and I am behind list discussions on certain areas myself.
>
> At least my latest patch series received two positive reviews. ;-)
They are _not_ even in 'pu'. I am talking about things that
have been cooking.
>> > ddiff --git a/t/Makefile b/t/Makefile
>>
>> ???
>
> Remnant of a change to that file which was later reverted but mtime
> doesn't match the index.
Double 'd'?
next prev parent reply other threads:[~2007-04-10 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 21:32 [PATCH 11/10] allow forcing index v2 and 64-bit offset treshold Nicolas Pitre
2007-04-09 22:28 ` Junio C Hamano
2007-04-09 22:33 ` Bill Lear
2007-04-09 23:04 ` Nicolas Pitre
2007-04-10 0:23 ` Junio C Hamano [this message]
2007-04-10 1:03 ` Nicolas Pitre
2007-04-10 7:31 ` Junio C Hamano
2007-04-10 13:23 ` Nicolas Pitre
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=7vejmtxekj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.