From: "Lars Hjemli" <hjemli@gmail.com>
To: "Luke Lu" <git@vicaya.com>
Cc: "Benoit SIGOURE" <tsuna@lrde.epita.fr>, git@vger.kernel.org
Subject: Re: git-svn questions: how to clone/init non-standard layout branches/tags?
Date: Sat, 3 Nov 2007 21:32:02 +0100 [thread overview]
Message-ID: <8c5c35580711031332y4018dba6y5d24965ebf2fbefb@mail.gmail.com> (raw)
In-Reply-To: <C81F0AB6-ED04-405F-AA29-CD72816FB7B9@vicaya.com>
On Nov 3, 2007 9:01 PM, Luke Lu <git@vicaya.com> wrote:
> On Nov 3, 2007, at 6:59 AM, Lars Hjemli wrote:
> > On Nov 3, 2007 11:56 AM, Benoit SIGOURE <tsuna@lrde.epita.fr> wrote:
> >> On Nov 3, 2007, at 9:19 AM, Luke Lu wrote:
> >>> 2. Is there a way to add a new svn branch like that (say production
> >>> or some_branch) to an existing git-svn repository that has trunk
> >>> cloned?
> >>
> >> I don't know, but that'd be great indeed.
> >>
> >
> > You can simply add "fetch" lines to the relevant "svn-remote" section
> > in .git/config.
>
> I did try to add a "fetch" line for the production branch like this:
>
> [svn-remote "svn"]
> url = svn+ssh://host/svn/project
> fetch = production:refs/remotes/svn-prod
> fetch = trunk:refs/remotes/git-svn
>
> which is modeled after http://lists-archives.org/git/420712-git-svn-
> remote-tracking-branch-question.html
>
> But when I try to checkout the production branch like this:
>
> git checkout -b prod remotes/svn-prod
>
> I got this:
> git checkout: updating paths is incompatible with switching branches/
> forcing
> Did you intend to checkout 'remotes/svn-prod' which can not be
> resolved as commit?
Did you forget to run 'git svn fetch' after modifying your .git/config?
--
larsh
next prev parent reply other threads:[~2007-11-03 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 8:19 git-svn questions: how to clone/init non-standard layout branches/tags? Luke Lu
2007-11-03 10:56 ` Benoit SIGOURE
2007-11-03 13:59 ` Lars Hjemli
2007-11-03 20:01 ` Luke Lu
2007-11-03 20:32 ` Lars Hjemli [this message]
2007-11-03 20:41 ` Luke Lu
2007-11-03 20:52 ` Lars Hjemli
2007-11-03 21:26 ` Luke Lu
2007-11-07 22:56 ` Luke Lu
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=8c5c35580711031332y4018dba6y5d24965ebf2fbefb@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=git@vicaya.com \
--cc=tsuna@lrde.epita.fr \
/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).