From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Thierry Volpiatto <thierry.volpiatto@gmail.com>
Subject: Re: git archive not updated since april 1st (no fooling)
Date: Thu, 19 May 2011 23:18:14 +0100 [thread overview]
Message-ID: <874o4qgwrd.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83wrhmfvwd.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 May 2011 20:22:10 +0300")
On 19 May 2011, Eli Zaretskii told this:
>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Thu, 19 May 2011 13:05:10 +0200
>>
>> 'bzr branch' fail always after 50mn about.
>
> Maybe for you, but not for everyone else. I had it run to completion
> on 4 different machines.
Older versions of bzr (e.g. 1.3) had exactly these symptoms when used
with certain proxies (I saw it with Polipo, which is a pretty standards-
compliant proxy as these things go).
Unsetting HTTP_PROXY before running bzr fixed it, but it still took
forever: bzr 2.3 is much much better.
--
NULL && (void)
next prev parent reply other threads:[~2011-05-19 22:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 15:07 git archive not updated since april 1st (no fooling) Randal L. Schwartz
2011-04-11 15:12 ` Bruce Stephens
2011-04-12 0:00 ` Christoph Scholtes
2011-04-18 14:17 ` Randal L. Schwartz
2011-04-18 15:32 ` Thierry Volpiatto
2011-04-19 13:08 ` Stefan Monnier
2011-04-19 13:14 ` Thierry Volpiatto
2011-04-19 13:47 ` Stefan Monnier
2011-04-19 14:05 ` Thierry Volpiatto
2011-04-19 13:39 ` Óscar Fuentes
2011-05-02 20:15 ` Antoine Levitt
2011-05-18 17:57 ` Andreas Amann
2011-05-19 4:45 ` Thierry Volpiatto
2011-05-19 7:18 ` Antoine Levitt
2011-05-19 10:21 ` Ted Zlatanov
2011-05-19 17:21 ` Eli Zaretskii
2011-05-19 17:30 ` Ted Zlatanov
2011-05-19 11:05 ` Thierry Volpiatto
2011-05-19 17:22 ` Eli Zaretskii
2011-05-19 22:18 ` Nix [this message]
2011-05-19 17:19 ` Eli Zaretskii
2011-05-19 22:22 ` Antoine Levitt
2011-05-19 17:28 ` Glenn Morris
2011-05-19 7:28 ` Julien Danjou
2011-05-19 13:35 ` Mathias Megyei
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=874o4qgwrd.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.