From: Mark Levedahl <mlevedahl@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Johannes.Schindelin@gmx.de, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-bundle: fix pack generation.
Date: Tue, 06 Mar 2007 22:17:30 -0500 [thread overview]
Message-ID: <45EE2ECA.60403@gmail.com> (raw)
In-Reply-To: <7vhcsxkb8n.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> That one is caused by the broken revision traversal in 'master'
> and being worked on in 'next'. Care to try the one from 'next'
> instead?
using next as just pulled from kernel.org
(09890a9bce0bc27182bc1f74a34b53) ...
git>git bundle create test.bdl HEAD~1..HEAD
error: rev-list died 255
I have not found any rev-args set that avoids that error.
Mark
next prev parent reply other threads:[~2007-03-07 3:17 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 [this message]
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
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=45EE2ECA.60403@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.