From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: error out when the SVN connection fails during a fetch
Date: Sun, 03 Dec 2006 19:23:52 +0100 [thread overview]
Message-ID: <871wnget3b.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20061128220605.GA1253@localdomain> (Eric Wong's message of "Tue, 28 Nov 2006 14:06:05 -0800")
* Eric Wong:
> finish_report does seem to return a useful value indicating success
> or failure, so we'll just set a flag when close_edit is called
> (it is not called on failures, nor is abort_edit) and check
> the flag before proceeding.
It seems that this needs some kind of fine-tuning. Now that git-svn
uses HTTP keepalive connections, you get a HTTP request error once you
run into the server-side request limit. It seems a bit excessive to
next prev parent reply other threads:[~2006-12-03 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:06 [PATCH] git-svn: error out when the SVN connection fails during a fetch Eric Wong
2006-11-28 22:24 ` Eric Wong
2006-12-03 18:23 ` Florian Weimer [this message]
2006-12-04 8:52 ` Eric Wong
2006-12-04 8:56 ` Florian Weimer
2006-12-04 9:05 ` Eric Wong
2006-12-06 17:01 ` Florian Weimer
2006-12-06 19:01 ` Junio C Hamano
2006-12-06 19:45 ` 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=871wnget3b.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).