From: Longmin WANG <longminwang@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Difficulties Accessing git Repository
Date: Wed, 9 Oct 2013 10:03:00 +0800 [thread overview]
Message-ID: <CANtV9MmetRzcDH7pgT5Bu+OEiMdTH79NB1U62JEMwu--4PozyQ@mail.gmail.com> (raw)
In-Reply-To: <4D604098-3942-40FB-B713-29AF27778ACA@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On Wed, Oct 9, 2013 at 9:46 AM, Mike McLean <mike.mclean@pobox.com> wrote:
>
> On Oct 8, 2013, at 9:13 PM, Nick Dokos <ndokos@gmail.com> wrote:
>
> > Charles Millar <millarc@verizon.net> 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
<http://math.nankai.edu.cn/~wanglm/>
[-- Attachment #2: Type: text/html, Size: 3049 bytes --]
next prev parent reply other threads:[~2013-10-09 2:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 20:50 Difficulties Accessing git Repository Josiah Schwab
2013-10-02 21:12 ` Suvayu Ali
2013-10-08 17:32 ` Josiah Schwab
2013-10-08 22:11 ` Charles Millar
2013-10-09 1:13 ` Nick Dokos
2013-10-09 1:46 ` Mike McLean
2013-10-09 2:03 ` Longmin WANG [this message]
2013-10-09 4:17 ` Thomas S. Dye
2013-10-09 7:17 ` Carsten Dominik
2013-10-09 7:30 ` Suvayu Ali
2013-10-09 11:30 ` Charles Millar
2013-10-09 13:16 ` Jason Dunsmore
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 12:24 Susan Cragin
2013-11-05 11:03 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANtV9MmetRzcDH7pgT5Bu+OEiMdTH79NB1U62JEMwu--4PozyQ@mail.gmail.com \
--to=longminwang@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).