From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Simmons <jsimmons@infradead.org>
Cc: akpm <akpm@osdl.org>,
linux-fbdev-devel@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] MAINTAINERS: mark framebuffer as Orphan
Date: Wed, 21 Feb 2007 13:36:43 -0800 [thread overview]
Message-ID: <45DCBB6B.5040001@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702212136360.20620@pentafluge.infradead.org>
James Simmons wrote:
>>> ...
>> 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.
Sure. I'm not changing anything. :)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>, 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 13:36:43 -0800 [thread overview]
Message-ID: <45DCBB6B.5040001@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702212136360.20620@pentafluge.infradead.org>
James Simmons wrote:
>>> ...
>> 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.
Sure. I'm not changing anything. :)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-21 21:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 21:25 [PATCH] MAINTAINERS: mark framebuffer as Orphan 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 ` Antonino A. Daplas
2007-02-20 5:17 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-21 21:39 ` James Simmons
2007-02-21 21:39 ` [Linux-fbdev-devel] " James Simmons
2007-02-21 21:37 ` James Simmons
2007-02-21 21:37 ` James Simmons
2007-02-21 21:36 ` Randy Dunlap [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=45DCBB6B.5040001@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.