From: Matthias Urlichs <smurf@smurf.noris.de>
To: git@vger.kernel.org
Subject: Re: [BUG] git-svnimport doesn't import actual code
Date: Thu, 17 Nov 2005 18:05:23 +0100 [thread overview]
Message-ID: <pan.2005.11.17.17.05.21.780279@smurf.noris.de> (raw)
In-Reply-To: 20051117160645.GA26871@lumumba.uhasselt.be
Hi, Panagiotis Issaris wrote:
> git-svnimport -v svn://svn.berlios.de/rtnet/trunk
That's easy -- you can't svn-pull the trunk that way.
(Note that you got a lot of "skipped" messages...)
Just drop the "trunk", add a "-b branches" if that repository
needs it, and svnimport will handle it.
ASIDE: All the repositories in my import list need that flag, so I am
considering changing the default name from "branch" to "branches".
Objections, anybody?
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
It is impossible to travel faster than light, and certainly not desirable,
as one's hat keeps blowing off.
-- Woody Allen
prev parent reply other threads:[~2005-11-17 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 16:06 [BUG] git-svnimport doesn't import actual code Panagiotis Issaris
2005-11-17 17:05 ` Matthias Urlichs [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=pan.2005.11.17.17.05.21.780279@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=git@vger.kernel.org \
/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