From: linux@horizon.com
To: linux@horizon.com, nico@cam.org
Cc: git@vger.kernel.org, gitzilla@gmail.com
Subject: Re: A look at some alternative PACK file encodings
Date: 7 Sep 2006 15:16:22 -0400 [thread overview]
Message-ID: <20060907191622.7597.qmail@science.horizon.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609071228560.18635@xanadu.home>
> So I don't think we would gain that much using that encoding
> unless/until the pack format is made completely incompatible due to
> other changes, and that's something we should try to avoid as much as
> possible anyway.
Ah, I'm sorry; I didn't realize that it was already used elsewhere in
the pack format and this was just code re-use. That is indeed a good
reason to stick with what's already there.
I agree the savings are minimal, but if you're starting from scratch,
they're free, so why not use them? I tried to show that the code
complexity is truly negligible.
I'm sorry I didn't realize the details of pack structure before.
next prev parent reply other threads:[~2006-09-07 19:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 8:41 A look at some alternative PACK file encodings linux
2006-09-07 17:20 ` Nicolas Pitre
2006-09-07 19:16 ` linux [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-07 9:07 linux
2006-09-07 12:57 ` Jon Smirl
2006-09-07 13:34 ` linux
2006-09-07 14:19 ` Jon Smirl
2006-09-07 15:01 ` linux
2006-09-07 14:39 ` Richard Curnow
2006-09-07 17:40 ` Junio C Hamano
2006-09-07 17:22 ` A Large Angry SCM
2006-09-07 17:32 ` Nicolas Pitre
2006-09-07 19:22 ` linux
2006-09-06 21:47 A Large Angry SCM
2006-09-06 23:23 ` Jon Smirl
2006-09-06 23:39 ` A Large Angry SCM
2006-09-06 23:56 ` Linus Torvalds
2006-09-07 0:10 ` Jon Smirl
2006-09-07 0:06 ` David Lang
2006-09-07 0:19 ` A Large Angry SCM
2006-09-07 0:45 ` Linus Torvalds
2006-09-07 0:37 ` Nicolas Pitre
2006-09-07 0:04 ` Jon Smirl
2006-09-07 5:41 ` Shawn Pearce
2006-09-07 5:34 ` Shawn Pearce
2006-09-07 0:40 ` Nicolas Pitre
2006-09-07 0:59 ` Jon Smirl
2006-09-07 2:30 ` Nicolas Pitre
2006-09-07 2:33 ` A Large Angry SCM
2006-09-07 1:11 ` Junio C Hamano
2006-09-07 2:47 ` Nicolas Pitre
2006-09-07 4:33 ` Shawn Pearce
2006-09-07 5:27 ` Junio C Hamano
2006-09-07 5:46 ` Shawn Pearce
2006-09-07 18:50 ` Junio C Hamano
2006-09-07 5:21 ` Shawn Pearce
[not found] ` <9e4733910609061617m6783d6c4xaca2f9575e12d455@mail.gmail.com>
2006-09-07 5:39 ` 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=20060907191622.7597.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--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 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).