From: Nick Hengeveld <nickh@reactrix.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] HTTP partial transfer support for object, pack, and index transfers
Date: Fri, 30 Sep 2005 16:27:47 -0700 [thread overview]
Message-ID: <20050930232747.GB15593@reactrix.com> (raw)
In-Reply-To: <7vk6gz6lpp.fsf@assigned-by-dhcp.cox.net>
On Fri, Sep 30, 2005 at 12:47:30AM -0700, Junio C Hamano wrote:
> I took a look at this patch. It did not cleanly apply anymore,
> but I merged it anyway, and then took the liberty of updating it
> further, according to your response to my earlier comments.
Sorry about that - we're actually using git as a back end to a content
distribution system, so I'm still learning the finer points of using it
for source control...
> They will appear near the tip of the proposed updates branch.
> I'd appreciate it if you could check it out and see I did not
> break things by mistake.
I've included a patch that fixes one small problem; I've tested partial
transfers of packs and objects with this applied and it looks good.
Don't unlink the temp file when an object transfer fails, so next attempt
will pick up where the failed transfer left off
Signed-off-by: Nick Hengeveld <nickh@reactrix.com>
---
http-fetch.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
22226e509b916958a8b7aae76945c08d15ec686a
diff --git a/http-fetch.c b/http-fetch.c
--- a/http-fetch.c
+++ b/http-fetch.c
@@ -550,7 +550,6 @@ static int fetch_object(struct alt_base
curl_result = curl_easy_perform(curl);
curl_easy_setopt(curl, CURLOPT_HTTPHEADER, no_range_header);
if (curl_result != 0) {
- unlink(tmpfile);
return error("%s", curl_errorstr);
}
next prev parent reply other threads:[~2005-09-30 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 17:14 [PATCH] HTTP partial transfer support for object, pack, and index transfers Nick Hengeveld
2005-09-30 7:47 ` Junio C Hamano
2005-09-30 23:27 ` Nick Hengeveld [this message]
2005-10-01 7:17 ` Junio C Hamano
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=20050930232747.GB15593@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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;
as well as URLs for NNTP newsgroup(s).