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

Re: life cycle documentation

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Oct 27, 2014, 23:02 UTC
Message-ID
<20141027230209.GB422734@vauxhall.crustytoothpaste.net>
In-Reply-To
<544E5C2F.3090800@rackspace.com>
On Mon, Oct 27, 2014 at 09:52:31AM -0500, Ben Harper wrote:
Show 6 quoted lines
> Thanks for the clarification.  Someone in IRC mentioned the maintain-git.txt
> file.  I skimmed it and searched for some keywords, but was unable to find
> the information I needed.
> 
> Do you feel a RELEASES document is needed or is the maintain-git.txt file
> sufficient?

I don't personally feel one is needed. However, I'm a semi-regular on the list, so my opinion of what would be helpful to people less familiar with the project is going to be skewed. If you were to send a patch to add a releases.txt file in the Documentation directory, it would probably be welcome.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Ben Harper
Message 4 of 4 in “life cycle documentation”
  1. Ben HarperOct 23, 2014
  2. brian m. carlsonOct 24, 2014
  3. Ben HarperOct 27, 2014
  4. brian m. carlsonOct 27, 2014

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.