From: Nick Hengeveld <nickh@reactrix.com>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: New release?
Date: Tue, 6 Jun 2006 09:46:18 -0700 [thread overview]
Message-ID: <20060606164618.GC3938@reactrix.com> (raw)
In-Reply-To: <1149610759.27253.9.camel@dv>
On Tue, Jun 06, 2006 at 12:19:19PM -0400, Pavel Roskin wrote:
> On Mon, 2006-06-05 at 23:02 -0700, Junio C Hamano wrote:
> > - http-fetch fixes from Nick, which looked obviously correct.
> > I would appreciate test reports from people who saw breakages
> > on this one.
>
> I'm still getting a segfault with the current git from the "next" branch:
>
> $ git-clone http://www.denx.de/git/linux-2.6-denx.git
> ...
> got 4160b8334c53e0881cdc12c1f7d3d54fff883772
> got 5f57f29efee48d84e235a8ff75a35e7e354227a7
> got 681a9c73a2a321850404d4856f4738be47e17d15
> got 29b0ddaa324e417abf153460d7d94fb67823a6ef
> got 23e7a5c7d2c13d98524b69f54378d887e1962fc8
> /home/proski/bin/git-clone: line 29: 27271 Segmentation fault git-http-fetch -v -a -w "$tname" "$name" "$1/"
>
> It takes about an hour with my connection from running the command to
> the segfault. It you have any idea how to speed it up, it would be very
> helpful.
I can't offer any suggestions wrt speeding it up, but I'll do what I can
to reproduce the problem here.
> If I comment out USE_CURL_MULTI, I get compile errors in http.c and
> http-push.c.
I just posted a fix for the compile errors. As noted there, I've done
very little testing of the fetch/push binaries when built with
USE_CURL_MULTI commented out.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2006-06-06 16:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0606052002530.5498@g5.osdl.org>
2006-06-06 6:02 ` New release? Junio C Hamano
2006-06-06 8:30 ` Johannes Schindelin
2006-06-06 10:27 ` Junio C Hamano
2006-06-06 12:42 ` Johannes Schindelin
2006-06-06 15:20 ` Junio C Hamano
2006-06-06 16:08 ` Jon Loeliger
2006-06-06 17:15 ` Junio C Hamano
2006-06-06 17:58 ` Jon Loeliger
2006-06-06 16:19 ` Pavel Roskin
2006-06-06 16:46 ` Nick Hengeveld [this message]
2006-06-06 18:38 ` Pavel Roskin
2006-06-07 5:35 ` http-fetch segfault fix? Junio C Hamano
2006-06-07 5:41 ` Pavel Roskin
2006-06-07 5:58 ` Junio C Hamano
2006-06-07 14:29 ` Pavel Roskin
2006-06-07 15:32 ` Nick Hengeveld
2019-01-01 23:27 new release? Russell Coker
2019-01-02 23:44 ` Chris PeBenito
2019-01-05 1:50 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2020-11-29 23:37 New release? Laurent Bigonville
2020-12-01 4:30 ` Steve Grubb
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=20060606164618.GC3938@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.org \
--cc=torvalds@osdl.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 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.