From: Jeff King <peff@peff.net>
To: mav007ar <mav007ar@yahoo.com.ar>
Cc: git@vger.kernel.org
Subject: Re: Problem with git bundle.
Date: Wed, 30 Mar 2011 16:18:19 -0400 [thread overview]
Message-ID: <20110330201819.GB30663@sigill.intra.peff.net> (raw)
In-Reply-To: <1301488591248-6222619.post@n2.nabble.com>
On Wed, Mar 30, 2011 at 05:36:31AM -0700, mav007ar wrote:
> Hi everyone. I am using git-svn and I want transfer a repository using git
> bundle create ...
> Does anyone has the right steps to perform this task?
> Currently I'm doing the following.
>
> 1- git bundle create --all
> 2- git clone
> 3- cd into repository's directory just created.
> 4- Add [svn-remote "svn"]
> url = https://svn.swacorp.com/svn/commerce/trunk/commerce-project
> fetch = :refs/remotes/git-svn
> into the .git/config file.
> 5- git svn fetch svn.
>
> The problem is when I do the last step, I get ALL revisions with out
> considering the revision included into the bundle.
Clone will only clone what's in refs/heads of the bundle. In your case,
you also want the refs/remotes/git-svn branch (which is probably the
same as the "master" you bring across in the bundle).
So you could do this in the cloned repo:
git update-ref refs/remotes/git-svn master
And then your svn fetch should be much faster.
But note that git-svn also keeps some magic cache in .git/svn. If you
bring that information across, too, the initial fetch would probably be
faster. So I really wonder if what you want instead of bundle is to
simply tar up the .git directory of the original repo and copy the whole
thing to your destination.
-Peff
next prev parent reply other threads:[~2011-03-30 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 12:36 Problem with git bundle mav007ar
2011-03-30 20:18 ` Jeff King [this message]
2011-03-31 19:16 ` mav007ar
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=20110330201819.GB30663@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=mav007ar@yahoo.com.ar \
/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).