linux-kernel - Re: [Tux3] Current Activities?

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: <20090806075246.GA6860@elte.hu>
Date:	Thu, 6 Aug 2009 09:52:46 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Phillips <phillips@...nq.net>,
	Jeff Garzik <jgarzik@...ox.com>
Cc:	debian developer <debiandev@...il.com>,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>, tux3@...3.org,
	LKML <linux-kernel@...r.kernel.org>, corbet@....net
Subject: Re: [Tux3] Current Activities?

* Daniel Phillips <phillips@...nq.net> wrote:

> [...]  I will say this now: if we are invited to merge in the next 
> major release, or in -mm or whatever, we will happily do it. If we 
> are not invited to merge, nobody has any cause to complain about 
> progress slowing down. [...]

The thing is, if you are waiting for an 'invite to upstream Linux 
merge' that could be a _very_ long wait: i've yet to see a single 
one ever since i started hacking Linux ~14 years ago ;-)

The model that Linux has been following for the past 10+ years is 
for new kernel projects to request inclusion. I.e. you push your 
patches upstream: you send patches and a pull request to the 
appropriate people/lists such as lkml.

This is done so because merging patches is a fundamentally 
hierarchical process, and the people merging _your_ patches are the 
real maintenance bottleneck, not you.

So it is not Linus and other maintainers who are searching the web 
for projects to merge and sending out 'invites' but the other way 
around: projects try to get upstream by submitting patches (which 
get reviewed and accepted or rejected).

So if you'd like your code to be merged upstream you better start 
this process now - this alone can take a lot of time: months (or 
years in certain cases). But it is still a much shorter time-span 
than an 'invite to merge' ;-)

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