LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] MAINTAINERS: mark framebuffer as Orphan
Date: Wed, 21 Feb 2007 21:37:50 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0702212136360.20620@pentafluge.infradead.org> (raw)
In-Reply-To: <20070216122403.GM13958@stusta.de>
> > > Alot of patches have been flowing into the layer.
> >
> > So would you like to leave it as Maintained or change it to
> > "Odd Fixes"? (Maintained => a maintainer) From the MAINTAINTERS file:
> >
> > Supported: Someone is actually paid to look after this.
> > Maintained: Someone actually looks after it.
> > Odd Fixes: It has a maintainer but they don't have time to do
> > much other than throw the odd patch in. See below..
> > Orphan: No current maintainer [but maybe you could take the
> > role as you write your new code].
> > Obsolete: Old code. Something tagged obsolete generally means
> > it has been replaced by a better system and you
> > should be using that.
> >...
>
> If you start doing this, there are a lot more entries that need to be
> changed...
>
> Which of Supported/Maintained/"Odd Fixes" is written doesn't matter in
> practice.
>
> What matters is that James' email address gets into the entry so that
> patches and bug reports reach him.
>
> James' work is definitely no below the average of entries marked as
> Maintained.
At this point I would say maintained. Plus Tony is coming back :-)
Its just recently I have been working on various other things like the
display class.
next prev parent reply other threads:[~2007-02-21 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 21:25 Randy Dunlap
2007-02-15 22:26 ` James Simmons
2007-02-15 23:05 ` Randy Dunlap
2007-02-16 12:24 ` Adrian Bunk
2007-02-20 5:17 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-21 21:39 ` James Simmons
2007-02-21 21:37 ` James Simmons [this message]
2007-02-21 21:36 ` Randy Dunlap
2007-02-15 23:27 ` Andrew Morton
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=Pine.LNX.4.64.0702212136360.20620@pentafluge.infradead.org \
--to=jsimmons@infradead.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--subject='Re: [PATCH] MAINTAINERS: mark framebuffer as Orphan' \
/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
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).