From: magnuspalmer <magnus.palmer@jayway.com>
To: git@vger.kernel.org
Subject: Re: Migrating from subversion via git svn contains log entry, but not the file change in the branch.
Date: Tue, 4 May 2010 08:32:35 -0700 (PDT) [thread overview]
Message-ID: <1272987155533-5003911.post@n2.nabble.com> (raw)
In-Reply-To: <4BDEC3AE.90409@drmicha.warpmail.net>
Ok, I have a local copy of the Subversion repo not using svnsync to speed up
testing.
I also upgraded git and git-svn to 1.7.1
Svn is at 1.6.5
I do the git svn init as before, but with the
file://<path_to_local_svn_repo>
It is saying using higher level url, if that does anything?
I asume that this error message is what is causing my problem?
r10623 = 7191e343c78eb0705173c47b1f914da8b1c6d6f5 (refs/remotes/svn/trunk)
Found possible branch point:
file:///home/user/svn-repo/services/project/clients/branches/develop/pom.xml
=>
file:///home/user/svn-repo/services/project/clients/branches/release-1.1.0,
10623
Initializing parent: refs/remotes/svn/release-1.1.0@10623
W: Ignoring error from SVN, path probably does not exist: (160013):
Filesystem has no item: File not found: revision 101, path
'/services/clients/branches/develop/pom.xml'
W: Do not be alarmed at the above message git-svn is just searching
aggressively for old history.
This may take a while on large repositories
r9529 = f4b81a737c453f18ab613cb216f26671e24b5d6e
(refs/remotes/svn/release-1.1.0@10623)
r9812 = 9359c6b9aac2c753e484d3a6ba26c857f578ad15
(refs/remotes/svn/release-1.1.0@10623)
Found branch parent: (refs/remotes/svn/release-1.1.0)
9359c6b9aac2c753e484d3a6ba26c857f578ad15
Following parent with do_switch
Invalid filesystem path syntax: Cannot replace a directory from within at
/usr/lib/git-core/git-svn line 5097
Btw, why do I get a @<revision> branch here?
remotes/svn/release-1.1.0
remotes/svn/release-1.1.0@10623
git checkout -b develop svn/develop
HEAD is now at 5012366... increased version to 1.2.0-SNAPSHOT
Version in file is not 1.2.0-SNAPSHOT as the log says and as it is in
Subversion.
--
View this message in context: http://git.661346.n2.nabble.com/Migrating-from-subversion-via-git-svn-contains-log-entry-but-not-the-file-change-in-the-branch-tp4997493p5003911.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2010-05-04 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:25 Migrating from subversion via git svn contains log entry, but not the file change in the branch magnuspalmer
2010-05-03 12:38 ` Michael J Gruber
2010-05-03 12:52 ` Dmitrijs Ledkovs
2010-05-04 15:20 ` magnuspalmer
2010-05-03 12:53 ` magnuspalmer
2010-05-04 15:32 ` magnuspalmer [this message]
2010-05-04 15:57 ` magnuspalmer
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=1272987155533-5003911.post@n2.nabble.com \
--to=magnus.palmer@jayway.com \
--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;
as well as URLs for NNTP newsgroup(s).