linux-kernel - Re: rfc: trivial patches and slow deaths?

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1308192315000.21654@pobox.suse.cz>
Date:	Mon, 19 Aug 2013 23:22:02 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Joe Perches <joe@...ches.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	kernel-janitors <kernel-janitors@...r.kernel.org>
Subject: Re: rfc: trivial patches and slow deaths?

On Mon, 19 Aug 2013, Joe Perches wrote:

> This is a 7 line patch that corrects logging defects that has had no 
> reply from you for the last month.
> 
> https://patchwork.kernel.org/patch/2833648/

This hasn't missed any Linus' major release, as it has been submitted post 
3.11 merge, right? (hint, that was Jul 4th).

If this would miss *next* major Linus' release, I would accept your 
complaints. But this is definitely not the case.

Joe, patience is a virtue. Especially when it comes to lower-priority 
stuff.

> I think that's overly long a time frame (any patch series will bitrot) 
> and too opaque for trivial patch submitters to have any idea what's 
> going on.

Again, only large, corss-subsystem series with a lot of maintainers CCed 
are generally delayed.

> Also, if you're concerned that the trivial tree wouldn't merge well in 
> next, 

That's not my concern. My concern is

- avoid work duplication
- avoid git history pollution (again, especially by trivial stuff)
- avoid unecessary stepping on maintainer's toes by something that has 
  such a low importance as trivial.git

Thanks for taking care,

-- 
Jiri Kosina
SUSE Labs
--
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/