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: Fri, 18 Aug 2006 10:49:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0608181041420.11359@localhost.localdomain> (raw)
In-Reply-To: <44E546F2.7070902@gmail.com>
On Thu, 17 Aug 2006, A Large Angry SCM wrote:
> Junio C Hamano wrote:
> ...
> > * "A Large Angry SCM" wrote a nice summary, "Git files data
> > formats documentation".
> >
> > Message-ID: <44D51D47.9090700@gmail.com>
> >
> > With one final update by Nico yesterday, I think it is ready
> > for inclusion.
> >
> > Does somebody care to make a patch out of it to add it to
> > Documentation/technical/, maybe removing pack-format.txt there
> > after making sure all it talks about is covered by the new
> > documentation?
> >
> > I do not have enough "virginity" to spot omissions in the
> > description anymore, so comments from somebody new to the
> > system are very much appreciated.
> >
>
> Two things:
>
> 1) I disagree with Nico's assessment that, other than his, there can not
> exist any type 2 packs that have bit 6 set to mean copy from result.
Care to explain why?
Since this code is mine I can tell you that no official GIT version ever
produced such a pack. The code to make use of that bit was quite
involving and the end result wasn't great at all so I never published
said code. This is also why current GIT accepts both pack version 2 and
3 without any distinction using the same code in patch-delta.c on the
basis that no version 2 packs ever used that bit.
Nicolas
next prev parent reply other threads:[~2006-08-18 14:49 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 [this message]
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
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.0608181041420.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).