The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Trouble wih TUHS rsync
Date: Sat, 21 Oct 2017 11:09:48 -0700	[thread overview]
Message-ID: <20171021181003.CBBA4156E7D7@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 21 Oct 2017 16:33:14 +1100." <alpine.BSF.2.21.1710211632350.30357@aneurin.horsfall.org>

On Sat, 21 Oct 2017 16:33:14 +1100 Dave Horsfall <dave at horsfall.org> wrote:
Dave Horsfall writes:
> Hmmm...  OK, thanks all; looks like I get to debug my firewall.

This is where a shell acct on a friends' system or your isp
can help.  That rescued me a number of times recently!


  reply	other threads:[~2017-10-21 18:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-21  0:52 Dave Horsfall
2017-10-21  1:37 ` Warren Toomey
2017-10-21  2:10   ` Dave Horsfall
2017-10-21  2:17     ` Will Senn
2017-10-21  3:34     ` Lyndon Nerenberg
2017-10-21  5:33     ` Dave Horsfall
2017-10-21 18:09       ` Bakul Shah [this message]
2017-10-22  0:16         ` Larry McVoy
2017-10-22  0:17         ` Dave Horsfall
2017-10-22  3:24         ` Steve Nickolas
2017-11-05  2:36       ` Dave Horsfall
2017-10-21  2:24   ` Steve Nickolas
2017-10-21 14:10 Nelson H. F. Beebe

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=20171021181003.CBBA4156E7D7@mail.bitblocks.com \
    --to=bakul@bitblocks.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.
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 NNTP newsgroup(s).