From: "Peter Harris" <git@peter.is-a-geek.org>
To: "Grzegorz Kossakowski" <grek@tuffmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to clone git repository with git-svn meta-data included?
Date: Sun, 7 Dec 2008 18:51:24 -0500 [thread overview]
Message-ID: <eaa105840812071551w2106eb72k54ec68938628d51@mail.gmail.com> (raw)
In-Reply-To: <493C47FD.4080302@tuffmail.com>
On Sun, Dec 7, 2008 at 5:02 PM, Grzegorz Kossakowski wrote:
> Peter Harris pisze:
>> After the git clone, I do the following:
>> git svn init -s svn://repo/sitory
>> git svn rebase
>>
>> No data is transferred[1], although 'git svn rebase' does spend a
>> minute or so reading the commit messages to rebuild its index.
>
> I've tried this method with Cocoon repository
> (http://jukka.zitting.name/git/?p=cocoon.git;a=summary) and got this error:
>
> git clone git://jukka.zitting.name/cocoon.git
> git svn init -s https://svn.eu.apache.org/repos/asf/cocoon/
> git svn rebase
> Unable to determine upstream SVN information from working tree history
Odd. Usually that indicates a lack of metadata, but that repo appears
to contain the right stuff. Beats me.
Peter Harris
next prev parent reply other threads:[~2008-12-07 23:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:15 How to clone git repository with git-svn meta-data included? Grzegorz Kossakowski
2008-12-07 8:43 ` Jacob Helwig
2008-12-08 0:03 ` Nick Andrew
2008-12-07 16:57 ` Peter Harris
2008-12-07 19:08 ` Grzegorz Kossakowski
2008-12-07 20:30 ` Peter Harris
2008-12-07 22:02 ` Grzegorz Kossakowski
2008-12-07 23:51 ` Peter Harris [this message]
2008-12-08 13:10 ` Michael J Gruber
2008-12-08 18:26 ` Grzegorz Kossakowski
2008-12-08 18:40 ` Peter Harris
2008-12-08 18:43 ` Grzegorz Kossakowski
2008-12-09 9:08 ` Sam Vilain
2008-12-09 20:57 ` Grzegorz Kossakowski
2008-12-09 8:53 ` Michael J Gruber
2008-12-08 16:10 ` Shawn O. Pearce
2008-12-08 19:04 ` Grzegorz Kossakowski
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=eaa105840812071551w2106eb72k54ec68938628d51@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=grek@tuffmail.com \
/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).