Gnus development mailing list
 help / color / mirror / Atom feed
From: Sean Doran <smd@ebone.net>
Cc: ding@gnus.org
Subject: Re: Store meta information with backends?
Date: 25 Aug 2000 08:24:18 +0200	[thread overview]
Message-ID: <52d7ix504t.fsf@sean.ebone.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 23 Aug 2000 18:27:44 +0200"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> But this would be nice for other backends, too.  For
> example, suppose I rsync my ~/Mail directory between
> home and work, but at home I'm using a different NNTP
> server, and at home I read my Hotmail mail.

Alternatively, store your mail in ~/imap/ and use IMAP 
at home and at work to read your mail without necessarily
copying all of it over; if the meta-information is kept in
the IMAP back-end, you don't need to synch anything on
these mailboxes, you just us a "longer connection" to the
IMAP daemon.

Storing metainformation with other backends (e.g. nnml) 
obviously helps in the rsync case, but it should also make
it possible to move a group wholesale from one backend to
another, without losing marks/scores/kills/etc.   For
example, if I have an nnml group locally and I want to
"share" it with myself via IMAP, a Group-level command
should migrate everything from the nnml group to a new
nnimap one, without losing state.

> What do you all think?

Yes, please.

        Sean.



      parent reply	other threads:[~2000-08-25  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-23 16:27 Kai Großjohann
2000-08-23 17:35 ` Steven E. Harris
2000-08-23 19:50 ` Simon Josefsson
2000-08-25  6:24 ` Sean Doran [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=52d7ix504t.fsf@sean.ebone.net \
    --to=smd@ebone.net \
    --cc=ding@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).