git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [linux-pm] Re: Storing Maintainers info around the kernel tree

From
RHRene Herman <rene.herman@gmail.com>
Date
Aug 16, 2007, 15:50 UTC
Message-ID
<46C47246.9020800@gmail.com>
In-Reply-To
<Pine.LNX.4.44L0.0708161128540.3757-100000@iolanthe.rowland.org>
On 08/16/2007 05:31 PM, Alan Stern wrote:
> Please remember that not everybody uses git.  The MAINTAINERS data 
> should be available in the kernel source itself.
It may be useful to generate a MAINTAINERS file into releases yes.

I must say though that "why?" would also be a question. I personally don't think there's a whole lot wrong with more and more expecting people who submit patches (for whom this automation is intended) to be using git. Back in the BK days there were lots of reasons for resisting any and all dependency on the source code management tool but there don't seem to be too many left today as far as I'm concerned.

If it's about non-developer users, I suspect it would to a fairly large degree be an "in theory" thing to expect that said user does want the information in a downloaded releases, but not in git, and not online where git-web could also easily display all the information right alongside the files.

But yes, sure, anything can be generated...
Rene.
Previous: Alan SternNext: Stefan Richter
Message 4 of 9 in “Storing Maintainers info around the kernel tree”
  1. Kyle MoffettAug 16, 2007
  2. Rene HermanAug 16, 2007
  3. Alan SternAug 16, 2007
  4. Rene HermanAug 16, 2007
  5. Stefan RichterAug 16, 2007
  6. Rene HermanAug 17, 2007
  7. Alan SternAug 17, 2007
  8. Rene HermanAug 17, 2007
  9. Stefan RichterAug 17, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.