lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 19 Mar 2012 17:03:49 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	joe@...ches.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: ipv4: Standardize prefixes for message
 logging

From: Joe Perches <joe@...ches.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@...ches.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."
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists