Re: recommended mail clients

[Lee Revell]

On Mon, 2005-12-26 at 14:18 -0500, Jeff Garzik wrote:
> Jaco Kroon wrote:
> > Lee Revell wrote:
> > 
> >>On Mon, 2005-12-26 at 12:09 -0600, Jason Munro wrote:
> >>
> >>
> >>>On 11:54:00 am 26 Dec 2005 Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> >>>
> >>><snip>
> >>>
> >>>>>Dare I say it, KMail has also been doing the Right Thing for a
> >>>>>long time. It will only line wrap things that you insert by
> >>>>>typing; pastes are left untouched.
> >>>>
> >>>>It seems that of all the popular mail clients only Thunderbird has
> >>>>this problem.  AFAICT it's impossible to make it DTRT with inline
> >>>>patches and even if it is the fact that most users get it wrong
> >>>>points to a serious usability/UI issue.
> >>>>
> >>>>Would a patch to add "Don't use Thunderbird/Mozilla Mail" to
> >>>>SubmittingPatches be accepted?  Then we can point the Mozilla
> >>>>developers at it (they have shown zero interest in fixing the problem
> >>>>so far) and hopefully this will light a fire under someone.
> > 
> > 
> > I would second that patch.
> 
> I would NAK such a patch.
> 
> Andrew Morton described a way to do it, some method using x cut buffers, 
> IIRC.
> 
> The best thing to do is use a custom script, though.  Other mailers can 
> be annoying as well, with regards to the References header, for example. 
>   And pine is awful, encoding plain text as base64.

For a maintainer who patch bombs LKML constantly a custom script is best
but for the casual contributor their mailer should just work.

The default Gnome and KDE mail clients work OK so why don't we just try
to get Thunderbird fixed or at least warn about it?  Casual contributors
are very likely to read SubmittingPatches.

I'm not trying to find the one true solution I'd just like to end the
constant low grade noise (and higher bug fix latency!) of "Please
resend, your patch is linewrapped" every few days.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/