emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: swflint@flintfam.org (Samuel W. Flint)
To: emacs-orgmode@gnu.org
Subject: Re: Git repository error
Date: Wed, 20 Dec 2017 11:14:24 -0600	[thread overview]
Message-ID: <87zi6dtj7z.fsf@curry.flintfam.org> (raw)
In-Reply-To: <87h8snkiqv.fsf@yandex.com> (Colin Baxter's message of "Mon, 18 Dec 2017 18:12:40 +0000")

>>>>> Colin Baxter writes:

>>>>> Marco Wahl <marcowahlsoft@gmail.com> writes:
    >> Jack Kamm <jackkamm@gmail.com> writes:
    >>> I'm having the same issue as Josiah, are others able to pull
    >>> from the git repo?

    >> git pull works for me.

    >> Maybe the following questions lead to a better understanding.

    >> What about performing a plain

    >> git pull

    >> instead of make update?

    >> What about a fresh git clone?


    CB> I've just entered "git pull" and I get the same "Connection
    CB> reset by peer" error as before.

I'm still having this problem

    CB> -- Colin Baxter m43cap@yandex.com
    CB> ---------------------------------------------------------------------
    CB> GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5
    CB> 41C8
    CB> ---------------------------------------------------------------------
    CB> The sole cause of all human misery is the inability of people to
    CB> sit quietly in their rooms.  Blaise Pascal, 1670


-- 
Samuel W. Flint
4096R/266596F4
      (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
λs.(s s) λs.(s s)

  reply	other threads:[~2017-12-20 17:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 15:40 Git repository error Josiah Schwab
2017-12-15 18:06 ` Jack Kamm
2017-12-18 16:28   ` Marco Wahl
2017-12-18 17:40     ` Detlef Steuer
2017-12-18 18:52       ` Nick Dokos
2017-12-18 19:44         ` Thomas S. Dye
2017-12-18 19:50         ` Colin Baxter
2017-12-18 21:33           ` Nick Dokos
2017-12-19  7:31             ` Colin Baxter
2017-12-19 10:29             ` Achim Gratz
2017-12-18 20:02         ` Kaushal Modi
2017-12-18 22:13           ` Jonas Bernoulli
2017-12-18 18:12     ` Colin Baxter
2017-12-20 17:14       ` Samuel W. Flint [this message]
2017-12-20 18:03         ` lists
2017-12-21  7:10           ` Robert Klein
2017-12-21  7:25             ` Colin Baxter
2017-12-21 10:11               ` Eric S Fraga
2017-12-21 14:40                 ` Samuel W. Flint
2017-12-21 20:47                   ` Nick Dokos
2017-12-16  9:43 ` Detlef Steuer
2017-12-16 14:15   ` Kaushal Modi
2017-12-17 14:35   ` Charles Millar
  -- strict thread matches above, loose matches on Subject: below --
2017-05-25 23:10 Vicente Vera
2017-05-26  7:39 ` claude fuhrer
2017-05-26 10:35   ` Gregor Zattler
2017-05-26 12:08     ` Charles Millar
2017-05-26 14:38       ` Marcin Borkowski
2017-05-27  0:45   ` Luke
2017-05-27 19:46     ` Colin Baxter
2017-05-28  7:40   ` claude fuhrer
2017-05-28  9:28     ` Colin Baxter
2017-05-27 20:50 ` John Hendy
2017-05-27 22:47   ` Leslie Watter
2017-05-28  3:12     ` Jason Dunsmore

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=87zi6dtj7z.fsf@curry.flintfam.org \
    --to=swflint@flintfam.org \
    --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).