Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Dave Abrahams <dave@boostpro.com>,  ding@gnus.org
Subject: Re: Auto-slave gnusae?
Date: Mon, 08 Feb 2016 18:27:54 +0100	[thread overview]
Message-ID: <8760xzkt7p.fsf@linux-m68k.org> (raw)
In-Reply-To: <87fux3g4p2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 08 Feb 2016 16:18:49 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> But I guess that's what's Gnus slaves do, anyway...  But will the
> "other" running Gnus detect the slave data automatically without doing
> anything?

That's the whole point of Gnus slaves.

(gnus) Slave Gnusae

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



      parent reply	other threads:[~2016-02-08 17:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  0:33 Dave Abrahams
2016-02-06  5:54 ` Lars Ingebrigtsen
2016-02-07 15:57   ` Dave Abrahams
2016-02-08  5:18     ` Lars Ingebrigtsen
2016-02-08 14:27       ` Dave Abrahams
2016-02-09  4:16         ` Lars Ingebrigtsen
2016-02-10 20:53           ` Dave Abrahams
2016-02-08 17:27       ` Andreas Schwab [this message]

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=8760xzkt7p.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=dave@boostpro.com \
    --cc=ding@gnus.org \
    --cc=larsi@gnus.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.
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).