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, 23 Nov 2009 22:09:52 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Sam Ravnborg <sam@...nborg.org>,
	Américo Wang <xiyou.wangcong@...il.com>
Subject: Re: Stepping down as kbuild maintainer

Aníbal Monsalve Salazar napsal(a):
> On Sat, Nov 21, 2009 at 08:46:14AM +0100, Sam Ravnborg wrote:
>> On Sat, Nov 21, 2009 at 12:44:47PM +1100, Aníbal Monsalve Salazar wrote:
>>> Will you be available to answer questions while I walk the learning
>>> curve? :)
>> I will be around yes - as long as you do not expect too quick answers.
>> Good luck(*) if you decide to try it!
> 
> On Sat, Nov 21, 2009 at 09:56:39PM +0800, Américo Wang wrote:
>> On Sat, Nov 21, 2009 at 09:51:12PM +1100, Aníbal Monsalve Salazar wrote:
>>> I assume you can also help with most of the scripts. Right? :)
>> Sure, feel free to contact me if you need.
> 
> I would like to maintain kbuild.

Hi,

I would also like to maintain kbuild. Maybe we could work together? What
do you think? I already talked with Sam:

> On Mon, Nov 23, 2009 at 03:55:29PM +0100, Michal Marek wrote:
> > I would be interested / willing to take over kbuild maintainership
> > either alone or together with Aníbal who also expressed his interest. I
> > do have a linux-related job, actually kbuild-related (maintaining kernel
> > build infrastructure at a certain linux vendor) and my boss would allow
> > me to work on kbuild. I think have good experience with the kbuild
> > scripts, GNU make, perl, etc. Looking at the number of patches sent to
> > linux-kbuild, I think I should be able to manage that. And I only have
> > one kid so far ;-).
> 
> It helps enourmously if you anyway have do to some of the time consuming
> things at work.
> I suggest you and An?bal work out how to deal with stuff.
> 
> I will ocntinue to be around and can answer any questions - but the
> learning curve is maybe a bit steep in the beginning but then things
> gets easy.
> 
> And you are right - it has not been the # of patches to take care
> of. Only that to do stuff properly you should:
> - review carefully
> - test on 5+ architectures
> - and be responsive
> 
> So if you can put time aside for this a few times a week and maybe
> even the possibility to concentrate on something for more than 1 hour
> in row you should be fine.
> 
> Good luck!
> 
> 	Sam


Also, how is it supposed to work now technically - should we create a
new kbuild-{next,fixes}.git $somewhere, copy over the bits that are
currently in Sam's trees and start collecting & reviewing patches? And
once it's good enough, update the MAINTAINERS file?

Michal
--
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