From: "Avery Pennarun" <apenwarr@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Eric Wong" <normalperson@yhbt.net>, git@vger.kernel.org
Subject: Re: git-svn sucks when it should not
Date: Mon, 7 Jul 2008 12:29:43 -0400 [thread overview]
Message-ID: <32541b130807070929q65e9a0d8g788cdb8c28ef28b9@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807071242180.18205@racer>
On 7/7/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> # It heavily relies on curl being able to screen-scrape the directories,
> # in other words, it wants an HTTP on the other side that has directory
> # listings enabled.
I wrote a similar script myself, although it makes assumptions about
the meaning of /branches and /tags rather than using the dirs vs.
files trick.
Rather than relying on screen scraping with curl, you might prefer to
use "svn ls" instead, since it'll work with any svn-compatible
repository type and (I presume) doesn't require special web server
settings.
Have fun,
Avery
next prev parent reply other threads:[~2008-07-07 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 0:00 git-svn sucks when it should not Johannes Schindelin
2008-07-07 9:44 ` Eric Wong
2008-07-07 11:49 ` Johannes Schindelin
2008-07-07 16:29 ` Avery Pennarun [this message]
2008-07-07 17:18 ` Johannes Schindelin
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=32541b130807070929q65e9a0d8g788cdb8c28ef28b9@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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