From: Ben Bucksch <ben.bucksch.news@beonex.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Jeremy White <jwhite@codeweavers.com>, git@vger.kernel.org
Subject: Re: RFC re Thunderbird + imap-send
Date: Tue, 10 Feb 2009 13:24:40 +0100 [thread overview]
Message-ID: <49917208.6000807@beonex.com> (raw)
In-Reply-To: <49915FB6.8010803@drmicha.warpmail.net>
On 10.02.2009 12:06, Michael J Gruber wrote:
> For a typical text mail in Drafts I see lines like
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: quoted-printable
> Any chance we could use that rather than invoke the HTML editor?
> We would need to shut off q-p and f-f *and* avoid automatic word wrap
> (or make sure patches don't have longer lines then TBs editor allows),
> the latter I don't know how to do.
>
I'm not aware that existing headers would influence the send logic (in
turning on/off qp or f=f or word wrap).
next prev parent reply other threads:[~2009-02-10 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:49 RFC re Thunderbird + imap-send Jeremy White
2009-02-10 11:06 ` Michael J Gruber
2009-02-10 12:24 ` Ben Bucksch [this message]
2009-02-10 13:23 ` Jeremy White
2009-02-10 19:00 ` Jeremy White
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=49917208.6000807@beonex.com \
--to=ben.bucksch.news@beonex.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jwhite@codeweavers.com \
/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).