linux-kernel - Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

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:	Mon, 29 Jul 2013 08:11:41 -0600
From:	Jonathan Corbet <corbet@....net>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development
 process

On Mon, 29 Jul 2013 15:10:33 +0200
"Rafael J. Wysocki" <rjw@...k.pl> wrote:

> That actually is simple enough.
> 
> Check out the Linus' master branch and do
> 
> $ git log --ancestry-path --merges <commit>..

So I picked a recent, single-signoff patch mostly at random:

	8ade62857ef77bdf639185410fbcd811aa700cb2

That "git log" command gives me 156 intervening commits involving at least
a dozen networking trees, along with virtio, parisc, blackfin, x86, ...
Even if one stops looking at the first merge performed by Linus, that's 47
to look at.  Did that patch really pass through all those peoples' hands?

Plus, of course, this assumes there's no fast-forward merges in the mix.

>From your other message:

> And what about trusting maintainers?  If Linus trusts them enough to pull from
> them, why can't everybody else trust them enough to assume that they don't do
> bad things on purpose?

I hope you're not reading such thoughts into what *I* wrote.  But most
anybody who works on code occasionally does bad things by mistake, that's
why we have a review process.

jon
--
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/