From: Jeremy White <jwhite@codeweavers•com>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org, Ben Bucksch <ben.bucksch.news@beonex•com>
Subject: Re: [Virtual PATCH] Add an option to wrap a patch in <pre> in git-imap-send which ironically results in a cleaner patch from Thunderbird.
Date: Fri, 13 Feb 2009 07:50:38 -0600 [thread overview]
Message-ID: <49957AAE.7070505@codeweavers.com> (raw)
In-Reply-To: <49955860.80504@drmicha.warpmail.net>
Michael J Gruber wrote:
> Junio C Hamano venit, vidit, dixit 13.02.2009 05:19:
>> I do not think of a reason, other than to trigger the workaround you
>> mentioned in the documentation part of the patch, why any sane user would
>> want to send a patch as HTML. This configuration variable sounds more
>> like "imap.forceThunderbirdToSendNonFlowedTextByExploitingItsBug" than
>> "imap.html", in other words.
With Michael's proviso well in hand (it's a feature, not a bug), I
did want to say that I otherwise think this is a reasonable analysis.
In fact, calling the option imap.thunderbird-fixed-html is arguably a
better name.
Finally, I know it's my patch, but for the record, I won't be hurt if
it's round filed. You can make a clean case that not taking
it in leaves pressure on the joint dev communities to find a better
solution.
But the only better approach I can imagine is if Thunderbird were
to respect a 'format=fixed' injected in a message body. However,
as I think about that, I believe a correct Thunderbird implementation
of that would require having a per message setting for format.
The Thunderbird team is very reluctant to expose any UI on
f=f (see https://bugzilla.mozilla.org/show_bug.cgi?id=86607),
so having a per message UI element certainly sounds like a dead
idea walking :-/.
Cheers,
Jeremy
next prev parent reply other threads:[~2009-02-13 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 15:57 [Virtual PATCH] Add an option to wrap a patch in <pre> in git-imap-send which ironically results in a cleaner patch from Thunderbird Jeremy White
2009-02-13 4:19 ` Junio C Hamano
2009-02-13 11:24 ` Michael J Gruber
2009-02-13 13:50 ` Jeremy White [this message]
2009-02-13 14:47 ` Ben Bucksch
2009-02-13 17:49 ` Junio C Hamano
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=49957AAE.7070505@codeweavers.com \
--to=jwhite@codeweavers$(echo .)com \
--cc=ben.bucksch.news@beonex$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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