From: Jason Riedy <ejr@cs.berkeley.edu>
To: git@vger.kernel.org
Subject: [PATCH] git-svnimport: Allow direct access over https.
Date: Wed, 01 Feb 2006 13:31:56 -0800 [thread overview]
Message-ID: <7756.1138829516@lotus.CS.Berkeley.EDU> (raw)
I'm not sure what the benefits of "direct access" are,
but it works over https as well as http.
Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu>
---
git-svnimport.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
71596fc3eb8d2ea25bd8fc99c03d2171d4136d88
diff --git a/git-svnimport.perl b/git-svnimport.perl
index 6e3a44a..63339ef 100755
--- a/git-svnimport.perl
+++ b/git-svnimport.perl
@@ -141,7 +141,7 @@ if($opt_d or $opt_D) {
} else {
$svn_dir = "";
}
- if ($svn_url->scheme eq "http") {
+ if ($svn_url->scheme eq "http" || $svn_url->scheme eq "https") {
use LWP::UserAgent;
$lwp_ua = LWP::UserAgent->new(keep_alive => 1, requests_redirectable => []);
} else {
--
1.1.5.g4a2b
reply other threads:[~2006-02-01 21:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7756.1138829516@lotus.CS.Berkeley.EDU \
--to=ejr@cs.berkeley.edu \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).