public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "David Kågedal" <davidk@lysator•liu.se>
To: git@vger•kernel.org
Subject: git-svn usability
Date: Thu, 04 Jan 2007 18:34:52 +0100	[thread overview]
Message-ID: <87fyaqvgoz.fsf@morpheus.local> (raw)

I wanted to try out "git svn" and did a "git help svn" and got the man
page for git-svn.  That page starts out by describing that git-svn
only is useful for working with a single svn branch.  But then,
further down, it describes the commands "multi-init" and
"multi-fetch" anyway.  Confusing.  But I decided to give them a try.
But there isn't really any clear description on what the command line
should look like when you use multi-init (or any other git-svn command
for that matter).  So I boldly decided to try to run "git svn help
multi-init".  You never know, it might tell you something.  This is
what happened:

  morpheus% git svn help multi-init
  GIT_SVN_ID set to 'trunk' for help/trunk
  Initialized empty Git repository in /home/david/tmp/.git/
  W: --branches/-b not specified
  W: --tags/-t not specified

Not exactly what I wanted.  The command-line parser in git-svn is
broken since it picks the first argument that looks like a command
name.

-- 
David Kågedal

             reply	other threads:[~2007-01-04 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 17:34 David Kågedal [this message]
2007-01-05  2:02 ` [1/2 PATCH] git-svn: make multi-init less confusing Eric Wong
2007-01-05  6:37   ` David Kågedal
2007-01-05 15:38     ` Seth Falcon
2007-01-08 12:56       ` David Kågedal
2007-01-08 12:58       ` David Kågedal
2007-01-08 13:11         ` David Kågedal
2007-01-05  2:04 ` [PATCH 2/2] git-svn: update documentation for multi-{init|fetch} Eric Wong

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=87fyaqvgoz.fsf@morpheus.local \
    --to=davidk@lysator$(echo .)liu.se \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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