From: Shawn Pearce <spearce@spearce.org>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: Why do base objects appear behind the delta in packs?
Date: Tue, 29 Aug 2006 14:32:39 -0400 [thread overview]
Message-ID: <20060829183239.GH21729@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0608291410290.9796@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
> I look forward to being able to use your (and Jon's) fast-import work in
> order to play with (re)generation of big packs myself.
My repository is here:
http://www.spearce.org/projects/scm/git.git
branch 'refs/heads/sp/fastpack'.
I'd appreciate it if folks didn't clone directly from me but instead
used an existing clone to pull the branch down into. Its based on
a fairly recent 'next' branch. Anything not available via Junio's
'next' on kernel.org is loose objects in this repository and are
specific to my fast-import work.
Documentation of the protocol used to stuff a pack is in the
header of fast-import.c. Its a relatively trivial stream format.
It should be quite simple to generate a random large project and
pipe it into fast-import to get a resulting pack to play with.
I don't have Jon's cvs2svn code and I don't know if its ready for
public consumption yet. git-fast-import however looks like its
almost there, so I'm making the URL publicly available for those
that may be interested in it.
[Junio: please do the lazy thing and don't pull this into Git just
yet, I don't think this branch is ready for that, not even for pu.]
--
Shawn.
next prev parent reply other threads:[~2006-08-29 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 13:42 Why do base objects appear behind the delta in packs? Shawn Pearce
2006-08-29 14:40 ` Nicolas Pitre
2006-08-29 14:58 ` Jakub Narebski
2006-08-29 16:27 ` Shawn Pearce
2006-08-29 17:34 ` Junio C Hamano
2006-08-29 17:44 ` Shawn Pearce
2006-08-29 18:16 ` Nicolas Pitre
2006-08-29 18:32 ` Shawn Pearce [this message]
2006-08-29 19:23 ` Jon Smirl
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=20060829183239.GH21729@spearce.org \
--to=spearce@spearce.org \
--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 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).