arn...@skeeve.com wrote:
> I would have thought most people would do 'git pull' instead of 'git clone'
> and that pulling wouldn't be quite as intensive, but who knows...
I think that these days most people do not keep persistent state. The
cynic in me assumes they are working from their phone.
On Wed, Feb 21, 2018 at 12:45:24PM -0700, Bob Proulx wrote:
> arn...@skeeve.com wrote:
> > I would have thought most people would do 'git pull' instead of 'git clone'
> > and that pulling wouldn't be quite as intensive, but who knows...
>
> I think that these days most people do not keep persisten
> Date: Wed, 21 Feb 2018 02:45:27 -0700
> From: Bob Proulx
> Cc: savannah-hackers-public@gnu.org
>
> Eventually I couldn't find an alternative to killing all of the git
> processes and waiting a bit before restarting the server. Hopefully
> as people start cloning again they won't all do it at o
Hi Bob,
See below.
Bob Proulx wrote:
> Arnold Robbins wrote:
> > I'm seeing terribly slow git response from Savannah, both in Israel
> > and from a machine on the US east coast. So I think the problem isn't
> > network related.
> ...
> > If anyone is awake (I know it's about 1:00 a.m. east coa
Arnold Robbins wrote:
> I'm seeing terribly slow git response from Savannah, both in Israel
> and from a machine on the US east coast. So I think the problem isn't
> network related.
...
> If anyone is awake (I know it's about 1:00 a.m. east coast time), please
> investigate.
I believe that one o
Eli Zaretskii wrote:
> It is extremely unresponsive lately. I type "git pull" and wait for
> several minutes(!) with nothing happening.
>
> Help!
I believe that one of the projects hosted must have announced a new
git release and that synchronice a lot of people trying to clone at
the same time.
