From: Sebastian Pipping <webmaster@hartwork.org>
To: Thomas Rast <trast@student.ethz.ch>
Cc: "Nicolas Sebrecht" <nicolas.s.dev@gmx.fr>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
git@vger.kernel.org
Subject: Re: [BUG?] Re: fail to svn clone debian's kernel repository
Date: Thu, 04 Mar 2010 03:03:19 +0100 [thread overview]
Message-ID: <4B8F14E7.5050000@hartwork.org> (raw)
In-Reply-To: <201003031533.13056.trast@student.ethz.ch>
On 03/03/10 15:33, Thomas Rast wrote:
> Combining this fix with the above config results in correct
> "continuous" history of trunk, whereas merely using the config above
> results in a disconnect at the move.
Thanks for your time to look into that!
After applying your ideas (which seem to work well) I end up with:
==================================================================
git svn init file://"${ABS_SVN_SOURCE}"
git config svn-remote.svn.fetch 'trunk:refs/remotes/trunk@1889'
git svn fetch -r1:1889
git svn init file://"${ABS_SVN_SOURCE}" \
--trunk=main/trunk
git config svn-remote.svn.tags 'main/tags/*:refs/tags/*'
git config svn-remote.svn.branches 'main/branches/*:refs/heads/*'
git svn fetch -r1890:HEAD
==================================================================
.git/config holds:
==================================================================
[..]
[svn-remote "svn"]
url = file:///[..]/portage-anon-svn-repo-dump
fetch = trunk:refs/remotes/trunk@1889
fetch = main/trunk:refs/remotes/trunk
tags = main/tags/*:refs/tags/*
branches = main/branches/*:refs/heads/*
==================================================================
Thought I'd paste that if anybody else is interested.
Sebastian
prev parent reply other threads:[~2010-03-04 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 16:05 [BUG?] fail to svn clone debian's kernel repository Uwe Kleine-König
2009-06-10 18:42 ` Uwe Kleine-König
2010-03-01 2:08 ` Sebastian Pipping
2010-03-02 19:54 ` [BUG?] " Nicolas Sebrecht
2010-03-03 1:20 ` Sebastian Pipping
2010-03-03 14:33 ` Thomas Rast
2010-03-04 2:03 ` Sebastian Pipping [this message]
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=4B8F14E7.5050000@hartwork.org \
--to=webmaster@hartwork.org \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
--cc=trast@student.ethz.ch \
--cc=u.kleine-koenig@pengutronix.de \
/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.