From: Steven Grimm <koreth@midwinter.com>
To: Patrick Doyle <wpdster@gmail.com>
Cc: 'git' <git@vger.kernel.org>
Subject: Re: git-svn error "Unable to extract revision information from commit ...~1"
Date: Wed, 27 Jun 2007 13:25:43 -0700 [thread overview]
Message-ID: <4682C7C7.7050603@midwinter.com> (raw)
In-Reply-To: <e2a1d0aa0706271031n3191a27fi41ca5ba3f14c3a51@mail.gmail.com>
Patrick Doyle wrote:
> Wouldn't the svn head be called "git-svn"?
> Should the first checkout be written as:
>
> git checkout -b tempbranch git-svn
>
> (In other words, were the "trunk" and "tempbranch" arguments swapped
> in your example?)
Yes, sorry, I swapped the arguments. Should indeed be "git checkout -b
(your new branch name) (svn head branch name)" rather than the other way
around. My apologies for not proofreading my message.
However, the name of the svn head branch depends on the version of
git-svn you're using, and how you cloned the svn repository. If you used
the -T/--trunk option, then the svn head branch will indeed be called
"trunk" (and you might also have other branches corresponding to
whatever branches you're tracking in the svn repository.) If you're not
using that option, then your svn tracking branch will be called
"git-svn" or "origin" depending on your git-svn version.
> Finally, what is the purpose of creating a new branch as part of that
> command?
You never ever want to work directly on the git-svn tracking branch. It
is considered a remote branch and while it is technically possible to
check it out and commit to it, you will almost certainly confuse git-svn
if you do.
Also, creating a new branch means you still have your original nonlinear
history easily accessible if you need it (just check out your old
branch.) You can certainly still get at the old history without creating
a new branch, but it's more awkward.
-Steve
prev parent reply other threads:[~2007-06-27 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 19:09 git-svn error "Unable to extract revision information from commit ...~1" Victor Bogado da Silva Lins
2007-06-27 1:50 ` Steven Grimm
2007-06-27 2:20 ` Junio C Hamano
[not found] ` <1182947236.21320.3.camel@omicron.ep.petrobras.com.br>
2007-06-27 16:57 ` Steven Grimm
[not found] ` <e2a1d0aa0706271031n3191a27fi41ca5ba3f14c3a51@mail.gmail.com>
2007-06-27 20:25 ` Steven Grimm [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4682C7C7.7050603@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--cc=wpdster@gmail.com \
/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).