Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Migrating to IMAP for real?  As a native method, anyway.
Date: 21 Feb 2001 15:38:54 -0500	[thread overview]
Message-ID: <5blmqz22ld.fsf@avocet.cs.rochester.edu> (raw)
In-Reply-To: <87wvajbx2f.fsf@mallet-assembly.org> (Michael Alan Dorman's message of "21 Feb 2001 12:28:08 -0800")

Michael Alan Dorman <mdorman@debian.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > Does anybody have experience with using nnimap as the native server?
> 
> Use it all the time.
> 
> > And what would be the least painful way to migrate from me having:
> > 
> > (setq gnus-select-method '(nntp "foo"))
> > (setq gnus-secondary-select-methods
> >       '((nnimap "" (nnimap-address "bar"))
> >         (nnml "")))
> > 
> > to me having this:
> > 
> > (setq gnus-select-method '(nnimap "" (nnimap-address "bar")))
> > (setq gnus-secondary-select-methods
> >       '((nnml "")
> >         (nntp "" (nntp-address "foo"))))
> > 
> > I'd like to keep all marks, if possible.  But of course, I only want
> > to do this if there won't be tons of problems.
> 
> I moved my existing stuff, created a "tentative" new configuration,
> started it, populated the group list, put my old config back, and
> edited GROUPS.eld directly based on differences between it and the
> "tentative" setup. :-)
> 
> I don't know if this qualifies as less than tons of problems.

Most of them don't count as problems, because he is Kai.  

Remember to write a tutorial about migration.

ShengHuo



  reply	other threads:[~2001-02-21 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 20:16 Kai Großjohann
2001-02-21 20:28 ` Michael Alan Dorman
2001-02-21 20:38   ` ShengHuo ZHU [this message]
2001-02-21 21:21     ` Kai Großjohann
2001-02-21 21:19   ` Kai Großjohann
2001-02-22 13:53 ` Christoph Rohland
2001-02-22 14:21   ` Paul Jarc
2001-02-23 17:16 ` Douglas K. Rand
2001-02-26  9:41 ` Christoph Rohland

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=5blmqz22ld.fsf@avocet.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).