From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] fix warning in tlbex.c for CONFIG_32BIT
Date: Wed, 5 Oct 2005 18:17:12 +0100 [thread overview]
Message-ID: <20051005171712.GJ2699@linux-mips.org> (raw)
In-Reply-To: <4343F5B2.3020509@avtrex.com>
On Wed, Oct 05, 2005 at 08:48:02AM -0700, David Daney wrote:
> 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.
Maybe a different style of work there. The submission style we're asking
people to follow here is exactly the same as on linux-kernel, netdev or
other kernel-related lists.
I just asked somebody; this is the answer I got:
<snip>
I have never had any luck getting mailers to send patches in a way that
no one complained about. In the end, I used this
http://www.speakeasy.org/~pj99/sgi/sendpatchset
I found the best way is to have a directory with patches like
001_part1.patch, 002_part2.patch etc with matching explainations in
001_part1.mail 002_part2.mail . I have a script that generates the final
mails and feeds them to sendpatchset
<snip>
The script may not be what you want but I guess I'll be something like it
to deal with the huge patchsets I'm sometimes fiddling with - like the
452 patch monster right now ...
Ralf
prev parent reply other threads:[~2005-10-05 17:17 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
2005-10-05 17:17 ` Ralf Baechle [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=20051005171712.GJ2699@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@avtrex.com \
--cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox