git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: A Large Angry SCM <gitzilla@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Unresolved issues #3
Date: Sun, 20 Aug 2006 19:10:23 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608201840310.11359@localhost.localdomain> (raw)
In-Reply-To: <44E68DCD.8010603@gmail.com>

On Fri, 18 Aug 2006, A Large Angry SCM wrote:

> Nicolas Pitre wrote:
> > On Fri, 18 Aug 2006, A Large Angry SCM wrote:
> >> That doesn't prove the non-existence of other code to do it.
> > 
> > So?  If the official and primary code for GIT doesn't support it, what 
> > is the point?  I'm telling you that if such packs exist they will simply 
> > barf with all official GIT releases later than v1.1.6 making your 
> > argument pointless.
> > 
> > I don't mind you documenting that historic intent for a bit that was 
> > never officially used, but at least let's document it right.
> 
> Historic fact. Between Thu May 19 08:56:22 2005 and Thu Feb  9 21:06:38
> 2006 bit 6 of the first byte of a delta hunk was interpreted to mean
> that the source of the copy was the result buffer. From Thu May 19
> 08:56:22 2005 on, the code to decode delta hunks in type 2 packs was
> available to everyone and anyone interested could make a pack encoder
> that would create packs that the core Git code would correctly read. The
> commit of Thu Feb  9 21:06:38 2006, d60fc, actually introduced a bug
> that would treat valid type 2 packs as invalid.

The "actually introduced a bug" sentence is your own interpretation not 
a _fact_.

And I simply disagree with that interpretation of yours.

I don't think this is worth arguing any further.


Nicolas

  reply	other threads:[~2006-08-20 23:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18  4:09 Unresolved issues #3 Junio C Hamano
2006-08-18  4:49 ` A Large Angry SCM
2006-08-18 14:49   ` Nicolas Pitre
2006-08-18 14:56     ` A Large Angry SCM
2006-08-18 15:30       ` Nicolas Pitre
2006-08-19  4:04         ` A Large Angry SCM
2006-08-20 23:10           ` Nicolas Pitre [this message]
2006-08-20 23:26             ` Junio C Hamano
2006-08-21  4:05               ` A Large Angry SCM
2006-08-18  5:10 ` Jeff King
2006-08-18  8:54 ` Catalin Marinas
2006-08-18  9:26   ` Junio C Hamano
2006-08-18  9:56     ` Catalin Marinas
2006-08-18  8:56 ` Jakub Narebski
2006-08-18 16:40 ` Aneesh Kumar K.V
2006-08-18 16:48   ` Jakub Narebski
2006-08-18 17:03     ` Aneesh Kumar K.V
2006-08-18 17:09       ` Jakub Narebski
2006-08-18 17:57 ` Jon Loeliger
2006-08-20 22:17   ` Junio C Hamano
2006-08-21  2:09     ` [PATCH] daemon: prepare for multiple services Junio C Hamano
2006-08-21  2:09     ` [PATCH] daemon: add upload-tar service Junio C Hamano
2006-08-23 23:19 ` Unresolved issues #3 Martin Langhoff
2006-08-25 21:22 ` Jakub Narebski
2006-10-06  6:26 ` Unresolved issues #4 Junio C Hamano
2006-10-06 10:56   ` Jakub Narebski
2006-10-06 16:11     ` Shawn Pearce
2006-10-06 16:04   ` Jon Loeliger
2006-10-06 16:12   ` Shawn Pearce
2006-10-06 16:53   ` A Large Angry SCM

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.0608201840310.11359@localhost.localdomain \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=gitzilla@gmail.com \
    --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).