From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: ipv4: Standardize prefixes for message logging
Date: Mon, 19 Mar 2012 17:03:49 -0400 (EDT) [thread overview]
Message-ID: <20120319.170349.957038489849471796.davem@davemloft.net> (raw)
In-Reply-To: <1332190804.6525.12.camel@joe2Laptop>
From: Joe Perches <joe@perches.com>
Date: Mon, 19 Mar 2012 14:00:04 -0700
> On Mon, 2012-03-12 at 17:35 -0700, Joe Perches wrote:
>> On Mon, 2012-03-12 at 17:05 -0700, David Miller wrote:
>> > From: Joe Perches <joe@perches.com>
>> > Date: Mon, 12 Mar 2012 10:03:32 -0700
>> > > Add #define pr_fmt(fmt) as appropriate.
>> > > Add "IPv4: ", "TCP: ", and "IPsec: " to appropriate files.
>> > > Standardize on "UDPLite: " for appropriate uses.
>> > > Some prefixes were previously "UDPLITE: " and "UDP-Lite: ".
>> []
>> > Looks good, and applied,
>> OK. I'll submit a similar change for net/ipv6 in awhile.
>
> Would you still take a similar IPv6: prefix
> change for net-next or should I wait until
> the next release cycle?
Sure why not, everyone else is being a complete idiot and submitting
all of their shit at the merge window openning.
I am backlogged every single time the merge window opens up, why do
you people wait until the last possible minute to submit things? Are
you all too selfish or too stupid to care?
Every single one of you know it's coming, you see several -rc releases
go out.
The merge window isn't a trigger to "get it done and submitted right
now."
Instead, it really means "too late."
next prev parent reply other threads:[~2012-03-19 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 4:36 [PATCH net-next] net: Convert printks to pr_<level> Joe Perches
2012-03-12 6:48 ` David Miller
2012-03-12 17:03 ` [PATCH net-next] net: ipv4: Standardize prefixes for message logging Joe Perches
2012-03-13 0:05 ` David Miller
2012-03-13 0:35 ` Joe Perches
2012-03-19 21:00 ` Joe Perches
2012-03-19 21:03 ` David Miller [this message]
2012-03-19 21:14 ` Joe Perches
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=20120319.170349.957038489849471796.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®