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

Re: Including the release notes in the git-1.5.0 release?

From
Junio C Hamano <junkio@cox.net>
Date
Feb 14, 2007, 16:27 UTC
Message-ID
<7vk5ykso02.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070213180541.GH8670@thunk.org>
Theodore Tso <tytso@mit.edu> writes:
Show 10 quoted lines
> What I've seen some projects do (including some commercial products)
> is to keep them around with the old file names.  So if we have
>
> Documentation/RELEASE-NOTES_1.5.0.txt
> Documentation/RELEASE-NOTES_1.6.0.txt
> Documentation/RELEASE-NOTES_1.7.0.txt
>
> and a symlink from RELEASE-NOTES to Documentation/RELEASE-NOTES-<cur_ver>.txt
>
> that would make a lot of sense....
Done.

I used to like reading pod/perl*delta.pod but these days they are tooooo long. Hopefully we can keep our release notes short and sweet. 

People might already have noticed that the latest docs at
	http://www.kernel.org/pub/software/scm/git/docs/
has link to older versions.
Previous: Theodore Tso
Message 4 of 4 in “Including the release notes in the git-1.5.0 release?”
  1. Theodore Ts'oFeb 13, 2007
  2. Junio C HamanoFeb 13, 2007
  3. Theodore TsoFeb 13, 2007
  4. Junio C HamanoFeb 14, 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.