From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: New Gnus and Exchange 2003 - Usable?
Date: Wed, 29 Sep 2010 11:46:24 -0500 [thread overview]
Message-ID: <87ocbgzee7.fsf@lifelogs.com> (raw)
In-Reply-To: <76sk0s3diy.fsf@dev-d01.ppllc.com>
On Wed, 29 Sep 2010 09:06:13 -0400 Jake Colman <colman@ppllc.com> wrote:
Jake> I've been avidly reading all the posts regarding Lars' rework of nnimap.
Jake> I currently use Xemacs 21.4.17 and No Gnus 0.7 (from an old CVS fetch).
Jake> Is it smart to pull the latest Gnus and jump on the bandwagon as an
Jake> Exchange 2003 IMAP user? Or should I wait a bit longer?
The Exchange fix became standard behavior IIRC.
Jake> How do I get fetch Gnus out of git? I guess I need to build a git
Jake> client too...
We could set up a daily tarball I guess, but is it hard for you to
install http://code.google.com/p/tortoisegit/ or something similar?
Ted
next prev parent reply other threads:[~2010-09-29 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 13:06 Jake Colman
2010-09-29 13:56 ` Robert Pluim
2010-09-29 18:04 ` Steinar Bang
2010-09-30 7:02 ` Reiner Steib
2010-09-30 7:40 ` Steinar Bang
2010-09-30 7:48 ` Steinar Bang
2010-10-03 11:35 ` Tibor Simko
2010-10-05 18:07 ` Tibor Simko
2010-09-29 16:46 ` Ted Zlatanov [this message]
2010-10-03 1:50 ` Jake Colman
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=87ocbgzee7.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).