From: Matthias Urlichs <smurf@smurf.noris.de>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] SVN import: Use one log call
Date: Wed, 30 Nov 2005 07:52:42 +0100 [thread overview]
Message-ID: <20051130065241.GY20418@kiste.smurf.noris.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0511292247591.3122@localhost.localdomain>
Hi,
Nicolas Pitre:
> Same here, with the following public repo: svn://mielke.cc/main/brltty
>
Same thing -- should work with a "-T main/brltty" option.
> Thing is the above repository is not _that_ weird. And with the real
> svn it produces a proper source tree of course, without any special
> options. So I would think git-svnimport should be able to do the same.
> No?
Sure. The problem is that svn doesn't have tags, branches, or different
projects; it's all just subdirectories with linked files.
So you need a good mapping from one to the other. In principle that's
simple, it's just that nobody has written the code for a more flexible
mapping from svn paths to tags / branch+subpath yet.
--
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
- -
"Adam may not have been so perfect after the 'fall," but he was
not so big a fool."
[Lemuel K. Washburn, _Is The Bible Worth Reading
And Other Essays_]
next prev parent reply other threads:[~2005-11-30 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 7:13 [PATCH] SVN import: Use one log call Matthias Urlichs
2005-11-29 20:22 ` Junio C Hamano
2005-11-30 2:46 ` Matthias Urlichs
2005-11-30 3:54 ` Nicolas Pitre
2005-11-30 6:52 ` Matthias Urlichs [this message]
2005-11-30 7:54 ` Junio C Hamano
2005-11-30 8:34 ` Matthias Urlichs
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=20051130065241.GY20418@kiste.smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.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