From: Andreas Schwab <schwab@linux-m68k.org>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Ramsay Jones" <ramsay@ramsay1.demon.co.uk>,
git@vger.kernel.org
Subject: Re: [regression] Newer gits cannot clone any remote repos
Date: Thu, 15 Nov 2012 00:15:03 +0100 [thread overview]
Message-ID: <m28va3epzc.fsf@igel.home> (raw)
In-Reply-To: <CACYvZ7g7nCgQmcnwJYxvx5hJ+Y8rCQOBQyWYLZOt8NT5BTwTrw@mail.gmail.com> (Douglas Mencken's message of "Wed, 14 Nov 2012 13:01:01 -0500")
Douglas Mencken <dougmencken@gmail.com> writes:
>>>> I cannot reproduce the problem (on openSUSE 12.2).
>>>
>>> You do need multiple CPU/multi-core machine, as I got it.
>>
>> Which is what I have.
>
> Then try to build *vanilla* git 1.8.0,
Which is what I did.
> not OpenSuSE's one (with a lot of patches inside srcrpm).
Which lot of patches?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-11-14 23:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 16:32 [regression] Newer gits cannot clone any remote repos Douglas Mencken
2012-11-12 17:12 ` Kevin
2012-11-12 19:35 ` Douglas Mencken
[not found] ` <CAO54GHA=r8WUK3okm2imVkoB=SuZ=3o+wwdwLr_rmPXhdFzG_g@mail.gmail.com>
2012-11-12 17:13 ` Douglas Mencken
2012-11-13 18:55 ` Ramsay Jones
2012-11-13 19:55 ` Douglas Mencken
2012-11-13 20:33 ` Douglas Mencken
2012-11-15 12:51 ` Nguyen Thai Ngoc Duy
2012-11-15 18:55 ` Ramsay Jones
2012-11-13 20:51 ` Torsten Bögershausen
2012-11-13 22:36 ` Andreas Schwab
2012-11-14 16:19 ` Douglas Mencken
2012-11-14 16:32 ` Andreas Schwab
2012-11-14 18:01 ` Douglas Mencken
2012-11-14 23:15 ` Andreas Schwab [this message]
2012-11-15 19:17 ` Ramsay Jones
2012-11-21 19:20 ` Douglas Mencken
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=m28va3epzc.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=dougmencken@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=tboegi@web.de \
/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.