All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Bucksch <ben.bucksch.news@beonex.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Jeremy White <jwhite@codeweavers.com>,
	"Boyd Stephen Smith Jr." <bss@iguanasuicide.net>,
	git@vger.kernel.org, mozeditor@floppymoose.com
Subject: Re: [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch.
Date: Mon, 09 Feb 2009 14:25:48 +0100	[thread overview]
Message-ID: <49902EDC.6020901@beonex.com> (raw)
In-Reply-To: <499022D3.3000200@drmicha.warpmail.net>

On 09.02.2009 13:34, Michael J Gruber wrote:
> Johannes Schindelin venit, vidit, dixit 08.02.2009 18:28:
>    
>> On Sun, 8 Feb 2009, Jeremy White wrote
>>> Essentially, the problem is well understood - Thunderbird uses
>>> format=flowed by default, which is what mangles the patches.
>>>        
>> I guess I'll start discouraging use of Thunderbird from now on.

Or you could just publish:
1. Prefs | Advanced | General | Config Editor...
2. "mailnews.send_plaintext_flowed" = false

The defaults should be best for the average user, not the rare 
programmer, who has no problem changing prefs.

f=f helps the normal user (and more importantly his recipient) by 
properly flowing text, which allows me to read with line lengths which 
are comfortable to read for me. It harms only in rare cases where 
line-endings are very important, *but* are not explicitly marked so. I 
think you can switch to "preformat" in the HTML editor and it would 
work, because we then know it's not flowing text, but I haven't tried 
it, because I attach such documents as txt / diff files.

As inline attachments, they'll show up inline in the msg viewer as well 
(which means I can read and copy&paste them), but are clearly separated 
from the body (which is assumed to be human-created natural language 
text), avoiding the problem mentioned here, and can easily be saved as 
file, opened in an external app etc.. I don't know why you didn't choose 
that way, but I assume you had your reasons. Just as we had our reasons 
for choosing f=f.

> I found git-send-email the more reliable and practical solution for 
> sending out patches. Put yourself in bcc and you'll have a copy in 
> TB's inbox or another folder (use filters).

Yup, I think that's the best way - git is using email only as protocol, 
so it's good to have special clients to that, as it's a really special use.

> <sarcasm style="reality: exaggerated;">
> Isn't that some Linux guy? How would he matter for Mozilla? Does he even
> know how to send HTML mail...
> </sarcasm>
>    
I don't think it's a matter of clue, it's a matter of background and 
attitude.

Ben

  reply	other threads:[~2009-02-09 13:35 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08  3:26 [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch Jeremy White
2009-02-08  5:10 ` Boyd Stephen Smith Jr.
2009-02-08 16:01   ` Jeremy White
2009-02-08 17:28     ` Johannes Schindelin
2009-02-09 12:34       ` Michael J Gruber
2009-02-09 13:25         ` Ben Bucksch [this message]
2009-02-09 13:36           ` Johannes Schindelin
2009-02-09 13:50             ` Michael J Gruber
2009-02-09 14:39               ` Boyd Stephen Smith Jr.
2009-02-09 13:52             ` Ben Bucksch
2009-02-09 14:49               ` Johannes Schindelin
2009-02-09 13:52             ` Thunderbird and patches (was Re: [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch.) Jeremy White
2009-02-09 14:18               ` Ben Bucksch
2009-02-09 15:38                 ` Jeremy White
2009-02-09 15:54                   ` Michael J Gruber
2009-02-09 16:24                     ` Ben Bucksch
2009-02-09 18:06                       ` Jeremy White
2009-02-09 18:54                       ` Brandon Casey
2009-02-09 19:09                         ` Ben Bucksch
2009-02-09 19:14                           ` Johannes Schindelin
2009-02-09 19:20                             ` Ben Bucksch
2009-02-09 19:30                               ` Brandon Casey
2009-02-09 19:51                                 ` Ben Bucksch
2009-02-09 19:59                                   ` Ben Bucksch
2009-02-09 21:03                                     ` Brandon Casey
2009-02-09 21:07                                       ` Brandon Casey
2009-02-09 22:01                                       ` Ben Bucksch
2009-02-09 22:13                                         ` Brandon Casey
2009-02-09 22:25                                           ` Ben Bucksch
2009-02-09 22:28                                             ` Brandon Casey
2009-02-09 22:46                                               ` Ben Bucksch
2009-02-10  1:00                                                 ` Brandon Casey
2009-02-09 19:33                             ` Brandon Casey
2009-02-09 20:09                               ` Johannes Schindelin
2009-02-10 10:07                                 ` Michael J Gruber
2009-02-12  4:37                                   ` Thunderbird and patches Miles Bader
2009-02-12 10:07                                     ` Michael J Gruber
2009-02-09 19:22                           ` Thunderbird and patches (was Re: [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch.) Brandon Casey
2009-02-09 19:00                       ` [PATCH] example patch corrupted by thunderbird Brandon Casey
2009-02-09 15:49                 ` Thunderbird and patches (was Re: [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch.) Michael J Gruber
2009-02-09 22:39               ` Thunderbird and patches Ben Bucksch
2009-02-09 22:55                 ` Jeremy White
2009-02-09 23:01                   ` Ben Bucksch
2009-02-10  1:41 ` [PATCH v2] Enable setting attach as the default in .gitconfig for git-format-patch Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2009-02-12 15:51 Jeremy White
2009-02-12 21:01 ` 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=49902EDC.6020901@beonex.com \
    --to=ben.bucksch.news@beonex.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bss@iguanasuicide.net \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jwhite@codeweavers.com \
    --cc=mozeditor@floppymoose.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.