From: Eduardo Pereira Habkost <ehabkost@mandriva.com>
To: Christian Biesinger <cbiesinger@web.de>
Cc: git@vger.kernel.org, Matthias Urlichs <smurf@smurf.noris.de>
Subject: git-svnimport -d and -D options (was Re: [PATCH] Use a relative path for SVN importing)
Date: Mon, 13 Feb 2006 18:52:43 -0200 [thread overview]
Message-ID: <20060213205243.GF4323@duckman.conectiva> (raw)
In-Reply-To: <1139672651713-git-send-email-cbiesinger@web.de>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
Hi,
On Sat, Feb 11, 2006 at 04:44:11PM +0100, Christian Biesinger wrote:
> The absolute path (with the leading slash) breaks SVN importing, because it then
> looks for /trunk/... instead of /svn/trunk/... (in my case, the repository URL
> was https://servername/svn/)
I've hit this bug today, and fortunately I've found the fix from
Christian. Thanks! :)
I am wondering if this bug was the initial reason why the -d and -D
options where added to git-svnimport.
Is there another real reason why the -d and -D options exist in
git-svnimport?
The documentation for the options say that the "wrong" option will die
with 40x, but the commit message[1] says something about "internal server
error". I don't know which one is right.
Mathias, couldn't be the errors you described in the commit message
related to this bug?
[1] http://www.kernel.org/git/?p=git/git.git;a=commit;h=25f6f325d7a8f7cb686a9ffd9fa2c00b3aa85a60
--
Eduardo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-13 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 15:44 [PATCH] Use a relative path for SVN importing Christian Biesinger
2006-02-11 17:04 ` Christian Biesinger
2006-02-13 20:52 ` Eduardo Pereira Habkost [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=20060213205243.GF4323@duckman.conectiva \
--to=ehabkost@mandriva.com \
--cc=cbiesinger@web.de \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.