From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Miller <davem@davemloft.net>
Cc: joe@perches.com, tilman@imap.cc, mac@melware.de,
isdn@linux-pingi.de, jslaby@suse.cz,
linux-kernel@vger.kernel.org, hjlipp@web.de,
gigaset307x-common@lists.sourceforge.net, jirislaby@gmail.com
Subject: Re: "whitespace coding style cleanup" broke coding style
Date: Wed, 29 Feb 2012 00:41:56 +0000 [thread overview]
Message-ID: <20120229004156.7d17302d@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120228.184246.556442272540134467.davem@davemloft.net>
On Tue, 28 Feb 2012 18:42:46 -0500 (EST)
David Miller <davem@davemloft.net> wrote:
>
> The truth is that isdn is unmaintained, so I just apply all ISDN
> patches directly after I review them, and I will continue to do so
> with impunity.
Except the Gigaset which has its own maintainer entry and active
maintainer...
next prev parent reply other threads:[~2012-02-29 0:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 8:59 Jiri Slaby
2012-02-27 11:19 ` Tilman Schmidt
2012-02-27 11:34 ` Jiri Slaby
2012-02-27 16:52 ` Joe Perches
2012-02-27 17:12 ` Jiri Slaby
2012-02-27 17:27 ` Joe Perches
2012-02-27 17:39 ` [PATCH net-next] gigaset: Use semicolons to terminate statements Joe Perches
2012-02-27 19:12 ` David Miller
2012-02-27 18:58 ` "whitespace coding style cleanup" broke coding style Jiri Slaby
2012-02-28 17:58 ` Tilman Schmidt
2012-02-28 22:05 ` Joe Perches
2012-02-28 23:08 ` Tilman Schmidt
2012-02-28 23:28 ` Joe Perches
2012-02-28 23:42 ` David Miller
2012-02-29 0:41 ` Alan Cox [this message]
2012-02-29 8:27 ` Armin Schindler
2012-02-29 19:32 ` Joe Perches
2012-02-29 11:05 ` Tilman Schmidt
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=20120229004156.7d17302d@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=gigaset307x-common@lists.sourceforge.net \
--cc=hjlipp@web.de \
--cc=isdn@linux-pingi.de \
--cc=jirislaby@gmail.com \
--cc=joe@perches.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
--cc=tilman@imap.cc \
/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
Powered by JetHome