[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20120524.162841.1075718556084465509.davem@davemloft.net>
Date: Thu, 24 May 2012 16:28:41 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: joe@...ches.com
Cc: anirban.chakraborty@...gic.com, netdev@...r.kernel.org,
Dept_NX_Linux_NIC_Driver@...gic.com
Subject: Re: [PATCH net-next 0/2] qlcnic: Bug fixes
From: Joe Perches <joe@...ches.com>
Date: Thu, 24 May 2012 13:24:38 -0700
> On Thu, 2012-05-24 at 16:06 -0400, David Miller wrote:
>> From: Anirban Chakraborty <anirban.chakraborty@...gic.com>
>> Date: Thu, 24 May 2012 14:06:54 -0400
>>
>> > Please apply to net-next.
>>
>> As I've stated at least 10 times this week, net-next is not open
>> and therefore submitting patches for net-next is not appropriate.
>
>> If people are not going to even read my announcements and
>> notifications of the states of the various GIT trees, I might as well
>> not make them at all.
>
> Perhaps setup a patchwork bot to autoreply to the
> sender only that these won't be looked at until
> after the merge window closes and train yourself
> to ignore the patchwork queue until then?
Sorry, people simply need to learn when it's appropriate to
submit patches.
Forcing them to resend at the appropriate time will train
their minds to take such things into consideration.
And if it's too bothersome to get them to resubmit, perhaps
they don't consider their patch important enough after all.
That's why we always handle situations like this by dropping things
and asking for a resend.
--
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