From: Daniel Phillips <phillips@innominate.de>
To: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Patches
Date: Thu, 25 Jan 2001 14:31:45 +0100 [thread overview]
Message-ID: <3A702AC1.A077A105@innominate.de> (raw)
In-Reply-To: <200101250611.f0P6BI418581@devserv.devel.redhat.com>
Alan Cox wrote:
>
> I seem to be getting more and more patches that have tabs/spaces
> broken and line wrap damage. I've dumped a pile in my queue including
> some pcmcia support for sh3 and the like
>
> If your patches are getting ignored please mail yourself a copy and
> check your mailer works. If you have problems use mime (Linus doesnt like
> mime I dont care)
Netscape is bad news for patches, both sending and receiving. On send
it wraps lines and doesn't let you see the wrapped version until after
it's sent - on receive it likes to convert tabs to spaces. Avoid.
I haven't tried mozilla yet. I should, because if Mozilla is similarly
broken at least we can fix it.
Kmail works fine.
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-25 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 6:11 Patches Alan Cox
2001-01-25 10:08 ` Patches David Woodhouse
2001-01-25 14:59 ` Patches Mike A. Harris
2001-01-25 10:23 ` Patches David Woodhouse
2001-01-25 13:31 ` Daniel Phillips [this message]
2001-01-25 13:41 ` Patches Chris Wedgwood
2001-01-25 20:22 ` Patches Thunder from the hill
2001-01-26 18:22 ` Patches Marc Mutz
2001-01-29 14:41 ` Patches Thunder from the hill
2001-01-25 13:42 ` Patches Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2013-03-07 10:02 Patches Miles Rout
2013-03-07 12:07 ` Patches Daniel Mack
2002-08-30 21:38 Patches Russell King
2001-01-18 6:34 Patches Alan Cox
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=3A702AC1.A077A105@innominate.de \
--to=phillips@innominate.de \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).