git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeremy White <jwhite@codeweavers.com>
Cc: git@vger.kernel.org
Subject: Re: Status of Thunderbird work
Date: Thu, 12 Feb 2009 18:16:17 +0100	[thread overview]
Message-ID: <49945961.3040506@drmicha.warpmail.net> (raw)
In-Reply-To: <499449A0.4060002@codeweavers.com>

Jeremy White venit, vidit, dixit 12.02.2009 17:09:
> Okay, I am now done with the due diligence I felt I had to do as
> penance for sending 14 wrapped and flowed patches to the wine-devel
> mailing list :-/.
> 
> To summarize, I have:
>   1.  Submitted a patch that,imho, improves the git documentation
>       on this subject.
>   2.  Revised a Mozillazine KB Entry to hopefully help others:
>       http://kb.mozillazine.org/Plain_text_e-mail_-_Thunderbird#Completely_plain_email
>   3.  Submitted a patch that implements Ben's suggestion to use <pre>
>       and ctype of html to trick Thunderbird into doing the right thing.
>   4.  Submitted a patch to allow attach to be the default for git-format-patch.
> 
> I am not wedded to #3 and #4; in fact, I'm about to go revise the Wine Git
> instructions to make it clear that --attach is a last resort, and not a preferred
> choice (the current Wine Wiki makes --attach look more preferable than it really is).
> 
> If the html patch went in, I would use it, chortling with evil glee
> each time I did so.
> 
> Additionally, Dscho has written a Thunderbird extension to facilitate
> sending patches.  That doesn't fit my ideal flow (I'm actually quite fond
> of git-imap-send :-/), but Michael Gruber seemed interested and he and
> Dscho may take it somewhere.

Well, I said I will stick with git-send-mail, but since I'm a TB user
(and extension author) I'll help making this available (once I got my
QuoteCollapse for TB 3 out of the door).

> Finally, Michael also communicated in a private email that he may

Yeah, private, what could that mean, pryyy-vet? ;)

> consider some sort of rethink around git-send-email and git-imap-send,

OK, it wasn't really meant that private. I think an option restructuring
is in order.

> which sounded intriguing to me, but way past my fair penance.

It is not up to the sinner to decide upon his penance! The Wine-devil
shall say the final verdict...

Cheers,
Michael

      reply	other threads:[~2009-02-12 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 16:09 Status of Thunderbird work Jeremy White
2009-02-12 17:16 ` Michael J Gruber [this message]

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=49945961.3040506@drmicha.warpmail.net \
    --to=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).