All,
I'm running the command svn2git -v --notags --branches REbranches <URL>
and I'm getting the following:
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
git checkout -b <new_branch_name>
HEAD is now at 38b1da3... Update NEO targets to point to NeoMain kernel
Running command: git branch -t NeoMain@34 remotes/NeoMain@34
error: unknown switch `t'
usage: git branch [options] [-r | -a] [--merged | --no-merged]
or: git branch [options] [-l] [-f] <branchname> [<start-point>]
or: git branch [options] [-r] (-d | -D) <branchname>
or: git branch [options] (-m | -M) [<oldbranch>] <newbranch>
Generic options
-v, --verbose be verbose
--track set up tracking mode (see git-pull(1))
--color use colored output
-r act on remote-tracking branches
--contains <commit> print only branches that contain the commit
--abbrev[=<n>] use <n> digits to display SHA-1s
Specific git-branch actions:
-a list both remote-tracking and local branches
-d delete fully merged branch
-D delete branch (even if not merged)
-m move/rename a branch and its reflog
-M move/rename a branch, even if target exists
-l create the branch's reflog
-f force creation (when already exists)
--no-merged <commit> print only not merged branches
--merged <commit> print only merged branches
Where did the -t come from? What is this telling me?
Thanks much.
Nolan
Hmmm, guess it wasn't that obvious to me!! :-)
I have 1.6.0.2 installed, which does support the --track option; did a later git support -t as well as --track?
git --version
git version 1.6.0.2
Is there some way to know what version of git the svn2git I have installed supports? And any way to get a version of svn2git that supports the one I have.
Thanks for your patience.
Nolan
________________________________________
From: Ævar Arnfjörð Bjarmason [avarab@gmail.com]
Sent: Monday, September 20, 2010 1:58 PM
To: Ring, Nolan
Cc: git@vger.kernel.org
Subject: Re: svn2git question: error: unknown switch `t'
On Mon, Sep 20, 2010 at 17:39, [off-list ref] wrote:
Where did the -t come from? What is this telling me?
git branch supports the -t or --track option. You obviously have too
old a git with too new a svn2git.
On Mon, Sep 20, 2010 at 19:19, [off-list ref] wrote:
Hmmm, guess it wasn't that obvious to me!! :-)
I have 1.6.0.2 installed, which does support the --track option; did a later git support -t as well as --track?
quoted
git --version
git version 1.6.0.2
Is there some way to know what version of git the svn2git I have installed supports? And any way to get a version of svn2git that supports the one I have.
You should just upgrade Git instead, using an old version of a
conversion tool is generally a Bad Idea.
Thanks for your quick response.
svn2git has alot of pre-requisite software. Can I just upgrade git and leave the other software at its current version?
Nolan
________________________________________
From: Ævar Arnfjörð Bjarmason [avarab@gmail.com]
Sent: Monday, September 20, 2010 3:30 PM
To: Ring, Nolan
Cc: git@vger.kernel.org
Subject: Re: svn2git question: error: unknown switch `t'
On Mon, Sep 20, 2010 at 19:19, [off-list ref] wrote:
Hmmm, guess it wasn't that obvious to me!! :-)
I have 1.6.0.2 installed, which does support the --track option; did a later git support -t as well as --track?
quoted
git --version
git version 1.6.0.2
Is there some way to know what version of git the svn2git I have installed supports? And any way to get a version of svn2git that supports the one I have.
You should just upgrade Git instead, using an old version of a
conversion tool is generally a Bad Idea.
At this point I feel like I'm chasing my tail.
I upgraded git and then started trying to upgrade other software that svn2git requires. It's been all downhill!
I found rpm 5.2.1 and tried installing it but needed popt. I found popt and installed it but now need beecrpypt because Python.h is missing. It looks like I need beecrypt but I *can't* find an appropriate beecrypt for Suse 11.
/bin/sh ../libtool --tag=CC --mode=compile gcc -m64 -DHAVE_CONFIG_H -I. -I.. -I. -I../include -I/usr/include/python2.6 -I/re/thirdparty_tools/java/linux/jdk1.6.0_02/jre/../include -I/re/thirdparty_tools/java/linux/jdk1.6.0_02/jre/../include/linux -DOPTIMIZE_X86_64 -O2 -DNDEBUG -Wa,--noexecstack -c -o _bc-py.lo _bc-py.c
libtool: compile: gcc -m64 -DHAVE_CONFIG_H -I. -I.. -I. -I../include -I/usr/include/python2.6 -I/re/thirdparty_tools/java/linux/jdk1.6.0_02/jre/../include -I/re/thirdparty_tools/java/linux/jdk1.6.0_02/jre/../include/linux -DOPTIMIZE_X86_64 -O2 -DNDEBUG -Wa,--noexecstack -c _bc-py.c -fPIC -DPIC -o .libs/_bc-py.o
_bc-py.c:8:20: error: Python.h: No such file or directory
In file included from _bc-py.c:14:
../include/beecrypt/python/mpw-py.h:12: error: expected specifier-qualifier-list before âPyObject_HEADâ
../include/beecrypt/python/mpw-py.h:20: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before âmpw_Typeâ
Am I doing something wrong here?
Thanks again for any insights.
Nolan
________________________________________
From: git-owner@vger.kernel.org [git-owner@vger.kernel.org] On Behalf Of nolan.ring@emc.com [nolan.ring@emc.com]
Sent: Monday, September 20, 2010 3:40 PM
To: avarab@gmail.com
Cc: git@vger.kernel.org
Subject: RE: svn2git question: error: unknown switch `t'
Thanks for your quick response.
svn2git has alot of pre-requisite software. Can I just upgrade git and leave the other software at its current version?
Nolan
________________________________________
From: Ævar Arnfjörð Bjarmason [avarab@gmail.com]
Sent: Monday, September 20, 2010 3:30 PM
To: Ring, Nolan
Cc: git@vger.kernel.org
Subject: Re: svn2git question: error: unknown switch `t'
On Mon, Sep 20, 2010 at 19:19, [off-list ref] wrote:
Hmmm, guess it wasn't that obvious to me!! :-)
I have 1.6.0.2 installed, which does support the --track option; did a later git support -t as well as --track?
quoted
git --version
git version 1.6.0.2
Is there some way to know what version of git the svn2git I have installed supports? And any way to get a version of svn2git that supports the one I have.
You should just upgrade Git instead, using an old version of a
conversion tool is generally a Bad Idea.