All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] fix warning in tlbex.c for CONFIG_32BIT
Date: Wed, 05 Oct 2005 08:48:02 -0700	[thread overview]
Message-ID: <4343F5B2.3020509@avtrex.com> (raw)
In-Reply-To: <20051005105336.GH2699@linux-mips.org>

Ralf Baechle wrote:
> On Tue, Oct 04, 2005 at 09:37:02PM -0700, David Daney wrote:
> 
>>Date:	Tue, 04 Oct 2005 21:37:02 -0700
>>From:	David Daney <ddaney@avtrex.com>
>>To:	linux-mips@linux-mips.org
>>Subject: [PATCH] fix warning in tlbex.c for CONFIG_32BIT
>>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
>                                                 ^^^^^^^^^^^^^
> 
> Applied - BUT: your mailer garbles patches ...
> 

Some people on this list are quite adamant that patches be in-line.

I was trying to see how my mailer (Thunderbird) handled this.  Obviously 
  (in hindsight) it screws things up.

Sending as an attachment works well except some mailers (Not 
Thunderbird) cannot quote attached patches with out jumping through hoops.

I don't really want to change the mailer that I am using, so I am in a 
bit of a bind WRT submitting patches here.

FWIW other mailing lists (binutils, gcc) don't seem to have the same 
trouble with attached patches.

David Daney

  reply	other threads:[~2005-10-05 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05  4:37 [PATCH] fix warning in tlbex.c for CONFIG_32BIT David Daney
2005-10-05 10:53 ` Ralf Baechle
2005-10-05 15:48   ` David Daney [this message]
2005-10-05 17:17     ` Ralf Baechle

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=4343F5B2.3020509@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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.