linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Sam Ravnborg" <sam@ravnborg.org>,
	"Américo Wang" <xiyou.wangcong@gmail.com>
Subject: Re: Stepping down as kbuild maintainer
Date: Mon, 23 Nov 2009 22:09:52 +0100	[thread overview]
Message-ID: <4B0AFA20.9090200@suse.cz> (raw)
In-Reply-To: <20091121224444.GA5296@master.debian.org>

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

  parent reply	other threads:[~2009-11-23 21:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 18:22 Stepping down as kbuild maintainer Sam Ravnborg
2009-11-20 18:26 ` [PATCH] kbuild: Steppeing down as Maintainer Sam Ravnborg
2009-11-20 19:20   ` tytso
2009-11-23 23:05   ` Andrew Morton
2009-11-24  9:15     ` maximilian attems
2009-11-25 19:50       ` Andrew Morton
2009-11-25  6:21   ` Stephen Rothwell
2009-11-25 17:24     ` Sam Ravnborg
2009-11-25 20:47       ` Michal Marek
2009-11-20 21:56 ` Stepping down as kbuild maintainer David Miller
2009-11-21  9:48 ` Américo Wang
2009-11-21 17:07   ` Randy Dunlap
2009-11-21 22:44 ` Aníbal Monsalve Salazar
2009-11-23 15:08   ` Steven Rostedt
2009-11-23 21:09   ` Michal Marek [this message]
2009-11-29  7:09     ` Aníbal Monsalve Salazar
2009-11-23 21:37 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2009-11-23 21:14 Jeffrey Haemer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0AFA20.9090200@suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).