From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Best way to keep 3 machines sync'ed
Date: Fri, 02 May 2003 20:40:11 +0200 [thread overview]
Message-ID: <ud6j1ur90.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <v97k99wbnf.fsf@crpppc215.epfl.ch>
marcuirl <marcuirl@imap.no2this.cc> writes:
>> What's the best way to keep them all so I don't have to read the same
>> news articles 3 times? If I copy my .newsrc, will it work across 2 news
>> servers? Will it keep track of what I've read on Slashdot also? Do I
>> need/want to copy my .newsrc.eld? Inquiring minds want to know... (TIA)
>
> I too have a similar situation to this above, maybe a little simpler!
While we're at it: The same goes for me. I want a options which tells
Gnus: "Put the MID of every article you mark read in a file" and a
command "update .newsrc from the file foo which contains MIDs of already
know articles".
--
WANTED: A nice signature
REWARD: none
next prev parent reply other threads:[~2003-05-02 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 15:41 Jason Dufair
[not found] ` <v97k99wbnf.fsf@crpppc215.epfl.ch>
2003-05-02 18:40 ` Frank Schmitt [this message]
2003-05-03 15:55 ` Kai Großjohann
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=ud6j1ur90.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).