git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Subject: git-svn branch naming question
Date: Sat, 8 Dec 2007 02:04:38 +0100	[thread overview]
Message-ID: <20071208010438.GE3199@genesis.frugalware.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

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?

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?

probably i miss some parameter to git-svn clone so that it would prefix
the refs with some 'origin'?

thanks,
- VMiklos

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-12-08  1:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  1:04 Miklos Vajna [this message]
2007-12-08 10:59 ` git-svn branch naming question Peter Baumann
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=20071208010438.GE3199@genesis.frugalware.org \
    --to=vmiklos@frugalware.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.
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).