From: Mark Levedahl <mlevedahl@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-bundle: avoid packing objects which are in the prerequisites
Date: Thu, 08 Mar 2007 15:36:41 -0500 [thread overview]
Message-ID: <45F073D9.7060209@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0703080039420.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
Using next (2432cbc253e8ef5cf09062abb8f7325813476d1d) that has your
patches for creating a thin-pack and limiting objects, I generally find
the bundle file created cannot be used.
Specific example you can repeat in a current git repo:
git>git branch foo 2432cbc253e8ef5c
git>git bundle create t.bdl foo~1..foo
Generating pack...
Done counting 20 objects.
Result has 14 objects.
Deltifying 14 objects.
100% (14/14) done
Writing 14 objects.
100% (14/14) done
Total 14 (delta 10), reused 10 (delta 6)
git>git fetch t.bdl
fatal: pack has junk at the end
error: index-pack exited with status 128
fatal: Fetch failure: t.bdl
git>
Also, we get an interesting failure if the references are not touched in
a given date range:
git>git bundle create t.bdl --since=5.minutes.ago foo
warning: ref 'foo' is excluded by the rev-list options
Generating pack...
Done counting 38321 objects.
Deltifying 38321 objects.
100% (38321/38321) done
Writing 38321 objects.
100% (38321/38321) done
Total 38321 (delta 26678), reused 38180 (delta 26551)
git>
No references requies 38000+ objects?? In this case, the bundle includes
every object in the repository, the exact opposite of what should happen
(zero objects).
Mark
next prev parent reply other threads:[~2007-03-08 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 4:17 builtin git-bundle - pack contains many more objects than required Mark Levedahl
2007-03-06 6:18 ` Junio C Hamano
2007-03-06 7:45 ` [PATCH] git-bundle: fix pack generation Junio C Hamano
2007-03-07 1:15 ` Mark Levedahl
2007-03-07 3:01 ` Junio C Hamano
2007-03-07 3:17 ` Mark Levedahl
2007-03-07 3:22 ` Johannes Schindelin
2007-03-07 3:50 ` Mark Levedahl
2007-03-07 4:05 ` Johannes Schindelin
2007-03-07 5:57 ` Junio C Hamano
2007-03-07 16:34 ` Mark Levedahl
2007-03-07 22:35 ` Johannes Schindelin
2007-03-07 23:17 ` Linus Torvalds
2007-03-08 0:27 ` [PATCH] git-bundle: Make thin packs Johannes Schindelin
2007-03-08 0:34 ` Linus Torvalds
2007-03-08 0:56 ` Johannes Schindelin
2007-03-08 2:02 ` Junio C Hamano
2007-03-08 13:07 ` Johannes Schindelin
2007-03-07 23:32 ` [PATCH] git-bundle: fix pack generation Junio C Hamano
2007-03-07 23:43 ` [PATCH] git-bundle: avoid packing objects which are in the prerequisites Johannes Schindelin
2007-03-08 20:36 ` Mark Levedahl [this message]
2007-03-07 1:16 ` [PATCH] git-bundle: fix pack generation Mark Levedahl
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=45F073D9.7060209@gmail.com \
--to=mlevedahl@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).