From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: [patch] (gnus)Splitting in IMAP
Date: Fri, 11 Jul 2003 12:03:10 +0200 [thread overview]
Message-ID: <m3znjle5y9.fsf@merlin.emma.line.org> (raw)
Hi,
I don't know the canonical way to send this, so here is some fodder for
the Gnus CVS committers, fixing grammar's off "Splitting in IMAP"
Section with gnus.texi. >:-) I presume these have been accidentally
omitted when reformulating. I didn't read the whole section, just fixed
the obvious ones. I wonder if Sieve (not mentioned) qualifies as
non-standard though ;-)
Index: texi/gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 6.534
diff -u -r6.534 gnus.texi
--- texi/gnus.texi 24 Jun 2003 08:12:31 -0000 6.534
+++ texi/gnus.texi 11 Jul 2003 10:12:46 -0000
@@ -16072,11 +16072,11 @@
@subsection Splitting in IMAP
@cindex splitting imap mail
-Splitting is something Gnus users has loved and used for years, and now
+Splitting is something Gnus users have loved and used for years, and now
the rest of the world is catching up. Yeah, dream on, not many
-@acronym{IMAP} server has server side splitting and those that have splitting
-seem to use some non-standard protocol. This means that @acronym{IMAP}
-support for Gnus has to do its own splitting.
+@acronym{IMAP} servers have server side splitting and those that have
+splitting seem to use some non-standard protocol. This means that
+@acronym{IMAP} support for Gnus has to do its own splitting.
And it does.
--
Matthias Andree
next reply other threads:[~2003-07-11 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 10:03 Matthias Andree [this message]
2003-07-11 13:30 ` Simon Josefsson
2003-07-11 15:17 ` Ted Zlatanov
2003-07-11 17:54 ` Simon Josefsson
2003-07-11 19:02 ` Jesper Harder
2003-07-11 20:40 ` Ted Zlatanov
2003-07-12 10:37 ` Simon Josefsson
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=m3znjle5y9.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
/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).