From: Randy Dunlap <randy.dunlap@oracle.com>
To: Paul Jackson <pj@sgi.com>
Cc: michael-lists@free-electrons.com, rob@landley.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] Documentation: mention email-clients.txt in SubmittingPatches
Date: Mon, 28 Jan 2008 12:58:41 -0800 [thread overview]
Message-ID: <479E4201.8040500@oracle.com> (raw)
In-Reply-To: <20080128133254.f70d50c2.pj@sgi.com>
Paul Jackson wrote:
> Randy wrote:
>> Does Sylpheed IMAP do filtering for you?
>>
>> It does not according to the Sylpheed FAQ, but the FAQ is
>> extremely out of date.
>
> You are correct that the Sylpheed FAQ, such as at:
>
> http://sylpheeddoc.sourceforge.net/en/faq/faq-1.html
>
> states:
>
> 1.8 Q08 Does Sylpheed have mail filtering?
> A. Yes. You can find it in Configuration -> filtering tab.
> Please note that filtering is not yet implemented for IMAP accounts.
>
> And you are correct -- that FAQ is out of date. It seems to be
> dated 2002.
>
> To answer your question, yes filtering now works fine on IMAP folders
> using Sylpheed. I make heavy use of it. I'm using Sylpheed version
> 2.2.4 at the moment.
>
> ===
>
> Be that as it may, whether Sylpheed IMAP folder filters worked or not,
> I'd suggest that the Documentation/email-clients.txt file not engage
> in evaluation of the general purpose feature sets of various email
> clients, but rather confine itself to what matters to the kernel
> mailing list, such as how to get patches formatted correctly.
Agreed. I'll modify it.
--
~Randy
next prev parent reply other threads:[~2008-01-28 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 10:20 [PATCH] Documentation: mention email-clients.txt in SubmittingPatches Michael Opdenacker
2008-01-18 16:34 ` Randy Dunlap
2008-01-28 15:52 ` Paul Jackson
2008-01-28 16:17 ` Randy Dunlap
2008-01-28 19:32 ` Paul Jackson
2008-01-28 20:58 ` Randy Dunlap [this message]
2008-01-28 21:20 ` Randy Dunlap
2008-01-28 21:49 ` Paul Jackson
2008-01-28 21:48 ` Paul Jackson
2008-01-18 20:35 ` Jeff Garzik
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=479E4201.8040500@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-lists@free-electrons.com \
--cc=pj@sgi.com \
--cc=rob@landley.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