public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "David Kågedal" <davidk@lysator•liu.se>
To: Eric Wong <normalperson@yhbt•net>
Cc: git@vger•kernel.org
Subject: Re: [1/2 PATCH] git-svn: make multi-init less confusing
Date: Fri, 05 Jan 2007 07:37:09 +0100	[thread overview]
Message-ID: <871wmaugh6.fsf@morpheus.local> (raw)
In-Reply-To: <20070105020158.GA21925@localdomain> (Eric Wong's message of "Thu, 4 Jan 2007 18:02:00 -0800")

Eric Wong <normalperson@yhbt•net> writes:

> It now requires at least one of the (trunk|branch|tags) arguments
> (either from the command-line or in .git/config).  Also we make
> sure that anything that is passed as a URL ('help') in David's
> case is actually a URL.

If I understand correctly, this still allows you to write

  $ git svn svn://foo/bar multi-init

which is kindof confusing.  But I guess it's less likely that anyone
does it by mistake.

Thanks for the quick response, anyway.  The documentation patch is
also a great improvement.

Now if you could only clarify the documentation of dcommit to explain
whether it creates one svn revision per commit in your branch, or if
it creates a single svn revision with the full diff, and the
documentation would be perfect :-)

-- 
David Kågedal

  reply	other threads:[~2007-01-05  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 17:34 git-svn usability David Kågedal
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 [this message]
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=871wmaugh6.fsf@morpheus.local \
    --to=davidk@lysator$(echo .)liu.se \
    --cc=git@vger$(echo .)kernel.org \
    --cc=normalperson@yhbt$(echo .)net \
    /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