On Wed, Oct 9, 2013 at 9:46 AM, Mike McLean wrote: > > On Oct 8, 2013, at 9:13 PM, Nick Dokos wrote: > > > Charles Millar writes: > > > >> Hello, > >> > >> On 10/8/2013 1:32 PM, Josiah Schwab wrote: > >>> Hi All, > >>> > >>>>> I just tried to pull from the main org-mode git repository. I > >>>>> encountered the following failure. > >>>>> > >>>>> ,---- > >>>>> | monolith:(stable) org-mode$ git pull > >>>>> | fatal: read error: Connection reset by peer > >>>>> `---- > >>>> I can confirm this issue. I successfully pulled earlier today though. > >>> This seems to be intermittent. It worked (~8 hours) later on October > 2. > >>> I tried to update a few minutes ago and again had a failure. > >>> > >>> Is there any other information that would be useful to report? I tried > >>> to pull while at my home (residential ISP) and then my work > >>> (university), and had failures both times. > >>> > >>> Josiah > >>> > >>> > >> This morning and just now I tried to update using > >> > >> cd ~/.elisp/org-mode && make update2 > >> > >> and the following failure resulted > >> > >> rm -f > >> git remote update > >> Fetching origin > >> fatal: read error: Connection reset by peer > >> error: Could not fetch origin > >> make: *** [up0] error 1 > >> > > > > I just [21:12:04 EDT] tried it and it worked. The question is: did > > somebody do something to bring it back or is it really intermittent? > > I couldn't pull this morning, nor just now. > > $ git --no-pager fetch origin > fatal: read error: Connection reset by peer > git exited abnormally with code 128. > > > > > I also failed to pull last night and this morning with the same errors. -- Longmin Wang (http://math.nankai.edu.cn/~wanglm/) Nankai University, 94 Weijin Road, Tianjin 300071, P. R. China