From: Eric Wong <e@80x24.org>
To: Jason Greenbaum <jgbaum@lji.org>
Cc: git@vger.kernel.org
Subject: Re: git svn clone of messy repository
Date: Thu, 11 Jan 2018 09:04:52 +0000 [thread overview]
Message-ID: <20180111090452.GA29874@dcvr> (raw)
In-Reply-To: <CAKNOR-JbAjE9URdFw_ZrqVeZot=emHFWLgpjhQ7uqUsJpRzx2A@mail.gmail.com>
Jason Greenbaum <jgbaum@lji.org> wrote:
> --trunk=trunk/project_of_interest \
> --branches=branches/FF-1.0/project_of_interest \
> --branches=branches/FF-1.1/project_of_interest \
> 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.
By default, the basename ("project_of_interest") is used and you
get collisions.
I think this section of the git-svn manpage should help:
| When using multiple --branches or --tags, 'git svn' does not automatically
| handle name collisions (for example, if two branches from different paths have
| the same name, or if a branch and a tag have the same name). In these cases,
| use 'init' to set up your Git repository then, before your first 'fetch', edit
| the $GIT_DIR/config file so that the branches and tags are associated
| with different name spaces. For example:
|
| branches = stable/*:refs/remotes/svn/stable/*
| branches = debug/*:refs/remotes/svn/debug/*
prev parent reply other threads:[~2018-01-11 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 0:29 git svn clone of messy repository Jason Greenbaum
2018-01-11 9:04 ` Eric Wong [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
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=20180111090452.GA29874@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jgbaum@lji.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).