From: Yasushi SHOJI <yashi@atmark-techno.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: SVN import
Date: Tue, 11 Oct 2005 05:21:48 +0900 [thread overview]
Message-ID: <87y851yvfn.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <20051010185729.GR567@kiste.smurf.noris.de>
At Mon, 10 Oct 2005 20:57:30 +0200,
Matthias Urlichs wrote:
>
> Yasushi SHOJI:
> > > True. I could add an option which behaves as if everything that's not
> > > recognized is seen as being on the trunk, but ...
> >
> > hmmm. can libsvn see those file had moved in to the trunk? don't know
> > how 'svn mv' is treated in svn.
> >
> see "svn log". The script sees the file, and where it comes from (but
> ignores that).
well, if it can, it'd be nice if svnimport could handle those
files. ;-)
anyway, here is another one if you are interested in. svnimport
doesn't seems to handle -t option, or what am i missing?
svnadmin create --fs-type fsfs /tmp/repo
svn co file:///tmp/repo test
cd test
svn mkdir foo
echo hello > foo/hello.c
svn add foo/hello.c
svn ci -m 'add hello.c'
cd ..
git-svnimport.perl -t foo -s2 -C /tmp/test.git -i -v file:///tmp/repo
DONE; creating master branch
cp: cannot stat `/tmp/test.git/.git/refs/heads/origin': No such file or directory
--
yashi
next prev parent reply other threads:[~2005-10-10 20:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 10:00 SVN import Matthias Urlichs
2005-10-10 9:45 ` Matthias Urlichs
2005-10-10 10:26 ` Elfyn McBratney
2005-10-10 11:04 ` Matthias Urlichs
2005-10-10 11:14 ` Elfyn McBratney
2005-10-10 11:39 ` Matthias Urlichs
2005-10-10 13:32 ` Matthias Urlichs
2005-10-10 17:48 ` Yasushi SHOJI
2005-10-10 18:13 ` Matthias Urlichs
2005-10-10 18:30 ` Yasushi SHOJI
2005-10-10 18:57 ` Matthias Urlichs
2005-10-10 20:21 ` Yasushi SHOJI [this message]
2005-10-10 20:52 ` Matthias Urlichs
2005-10-15 20:32 ` Kalle Valo
2005-10-15 20:44 ` svnimport: fixed Makefile entry Kalle Valo
2005-10-16 7:48 ` SVN import Junio C Hamano
2005-10-16 17:42 ` Matthias Urlichs
2005-10-16 18:09 ` Junio C Hamano
2005-10-16 17:58 ` 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=87y851yvfn.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.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.