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]
Date:	Thu, 03 Jan 2008 17:00:20 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Paolo Ciarrocchi <paolo.ciarrocchi@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	davem@...emloft.net, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: New branch for +1 kernel Was:Re: [PATCH] Use __u64 in aligned_u64's
 definition

Paolo Ciarrocchi wrote:
> This is something i was thinking to suggest.
> Kernel is made of a lot of different "areas" and the regression list
> is a great tool for monitoring every single area so why not opening a
> new branch and accepting patches only for areas which are not in the
> current regression list.?

Some regressions can't be easily associated with an "area".  And when
they can, consider the overhead involved with frequently kicking out
patchsets and taking them in again, based on when regressions become
known and when they are fixed, respectively.

> Sounds like a good way to be more strict about regressions and
> incentive people to solve regressions quicker.

To create such a motivation, that branch or tree would have to have a
practical use in development.  So what purpose would such a tree
fulfill, considering that we already have a myriad of topic trees and
the -mm tree for testing and preintegration?
-- 
Stefan Richter
-=====-==--- ---= ---==
http://arcgraph.de/sr/
--
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