From: Peter Baumann <waste.manager@gmx.de>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn branch naming question
Date: Sat, 8 Dec 2007 11:59:01 +0100 [thread overview]
Message-ID: <20071208105901.GA2844@xp.machine.xx> (raw)
In-Reply-To: <20071208010438.GE3199@genesis.frugalware.org>
On Sat, Dec 08, 2007 at 02:04:38AM +0100, Miklos Vajna wrote:
> hi,
>
> i'm using git-svn for projects where i don't just want to commit to
> trunk but to other branches, too.
>
> for example:
>
> git-svn clone -s svn+ssh://vmiklos@svn.gnome.org/svn/ooo-build ooo-build
>
> then i have a local 'master' branch and all the other branches are local
> branches.
>
> so, when i want to work in the ooo-build-2-3 branch, i do a:
>
> git checkout -b ooo-build-2-3 ooo-build-2-3
>
> but when i do a git svn rebase, i get:
>
> warning: refname 'ooo-build-2-3' is ambiguous.
>
> what am i doing wrong?
Try using 'git svn rebase remotes/ooo-build-2-3'.
git-svn should produce its branches under refs/remotes/* and your
local branches are under refs/heads/*.
By using 'git checkout -b ooo-build-2-3 ooo-build-2-3' you created
refs/heads/ooo-build-2-3 as a copy of refs/remotes/ooo-build-2-3 and now
using only ooo-build-2-3 is ambigious. (at least in some cases where git
won't take refs/heads/ooo-build-2-3)
>
> in fact i suspect that in case i would use some other branch name, like
> simply '2-3' then i could get rid of this warning, but that's the
> problem with using the equivalent name of the remote branch when working
> in a branch locally?
>
See above.
> probably i miss some parameter to git-svn clone so that it would prefix
> the refs with some 'origin'?
Look up --prefix in the manpage for git-svn.
-Peter
next prev parent reply other threads:[~2007-12-08 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 1:04 git-svn branch naming question Miklos Vajna
2007-12-08 10:59 ` Peter Baumann [this message]
2007-12-08 14:14 ` Miklos Vajna
2007-12-08 16:56 ` Peter Baumann
2007-12-08 23:52 ` Miklos Vajna
2007-12-09 2:05 ` Miklos Vajna
2007-12-09 2:13 ` Björn Steinbrink
2007-12-09 2:25 ` Miklos Vajna
2007-12-09 2:26 ` Eric Wong
2007-12-09 2:36 ` Miklos Vajna
2007-12-09 3:26 ` Eric Wong
2007-12-09 5:16 ` Harvey Harrison
2007-12-09 19:36 ` Miklos Vajna
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=20071208105901.GA2844@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).