From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] count-delta.c: Match the delta data semantics change in version 3.
Date: Thu, 09 Feb 2006 20:54:31 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602092053200.5397@localhost.localdomain> (raw)
In-Reply-To: <7vbqxg3tdd.fsf_-_@assigned-by-dhcp.cox.net>
On Thu, 9 Feb 2006, Junio C Hamano wrote:
> Junio C Hamano <junkio@cox.net> writes:
>
> > I agree with the general direction and this futureproofing is a
> > good thing to have before 1.2.0, I think.
> >
> > The bit is however _already_ looked at by the count_delta(),
> > to assess the extent of damage, IIRC. Should we be
> > futureproofing that bit as well?
>
> Something like this?
Right.
Nicolas
next prev parent reply other threads:[~2006-02-10 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 22:50 [PATCH] remove delta-against-self bit Nicolas Pitre
2006-02-09 23:53 ` Junio C Hamano
2006-02-10 1:17 ` [PATCH] count-delta.c: Match the delta data semantics change in version 3 Junio C Hamano
2006-02-10 1:54 ` Nicolas Pitre [this message]
2006-02-10 15:20 ` Nicolas Pitre
2006-02-10 17:19 ` Junio C Hamano
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=Pine.LNX.4.64.0602092053200.5397@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).