From: Jason Greenbaum <jgbaum@lji.org>
To: git@vger.kernel.org
Subject: git svn clone of messy repository
Date: Wed, 10 Jan 2018 16:29:12 -0800 [thread overview]
Message-ID: <CAKNOR-JbAjE9URdFw_ZrqVeZot=emHFWLgpjhQ7uqUsJpRzx2A@mail.gmail.com> (raw)
Hi,
I'm in the process of using git svn to migrate several repos over to
git and one repo, in particular, has a very challenging format.
During the migration, I would also like to reorganize the repo. It
looks something like this in svn:
myrepo
trunk
project_of_interest
other_project1
other_project2
…
branches
FF-1.0
project_of_interest
other_project1
other_project2
…
FF-1.1
project_of_interest
other_project1
other_project2
…
There is also a 'tags' directory at the toplevel, but that's not
important to illustrate the issue I'm having. What I would like to do
is to migrate ONLY the folder called 'project_of_interest' and
preserve it's trunk, branches, and tags. I'm not sure this is
possible directly with git svn clone, but here is what I've tried:
git svn clone \
--authors-file=$AUTHORS_FILE \
--prefix="" \
--trunk=trunk/project_of_interest \
--branches=branches/FF-1.0/project_of_interest \
--branches=branches/FF-1.1/project_of_interest \
svn://my-svn-server/myrepo \
project_of_interest.git
The trunk seems to become the 'master' branch just fine, but my svn
branches are not pulled down. I'm not sure I have the syntax right or
if this is even possible without first reorganizing the svn repo in
place, updating the .git/config file, or by some other means. Any
help would be much appreciated. I'm happy to provide more info as
needed.
Thanks,
Jason
next reply other threads:[~2018-01-11 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 0:29 Jason Greenbaum [this message]
2018-01-11 9:04 ` git svn clone of messy repository Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKNOR-JbAjE9URdFw_ZrqVeZot=emHFWLgpjhQ7uqUsJpRzx2A@mail.gmail.com' \
--to=jgbaum@lji.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).