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  linux-hardening  linux-cve-announce  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]
Message-ID: <20141217095227.GA8457@pd.tnic>
Date:	Wed, 17 Dec 2014 10:52:27 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Theodore Ts'o <tytso@....edu>
Cc:	Kevin Cernekee <cernekee@...il.com>,
	Jonathan Corbet <corbet@....net>,
	Thomas Gleixner <tglx@...utronix.de>,
	gnomes@...rguk.ukuu.org.uk,
	Brian Norris <computersforpeace@...il.com>,
	torvalds@...ux-foundation.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-doc@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 0/4] Stop maintainer abuse

On Wed, Dec 17, 2014 at 12:14:24AM -0500, Theodore Ts'o wrote:
>  And what's wrong for one maintainer will be right for another, and
> vice versa.

Ok, so what's wrong with "should not expect any feedback during the
merge window"?

If they get it, then that's fine. The formulation is loose on purpose.

And besides, when one starts working with maintainers, one soon learns
when they are the busiest and can refrain from sending patchsets then.

Or should we have subsystem maintainers each state whether they wanna
do patchsets during the merge window or not? Or are we bikeshedding
already?

I see your point that different maintainers can be busy at different
times but you also have to acknowledge the desire of some maintainers
not to get new patchsets during the merge window. So we have to have a
way to communicate that to submitters so that no explosions happen.

Oh, and also the
not-resend-in-under-a-week-and-wait-out-complete-review-first rule.
That's my personal pet peeve.

Ha, this sounds like a KS topic :-P

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ