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

Including the release notes in the git-1.5.0 release?

From
Theodore Ts'o <tytso@mit.edu>
Date
Feb 13, 2007, 14:13 UTC
Message-ID
<E1HGyPn-0003Te-9s@candygram.thunk.org>
Junio,

I noticed that the file v1.5.0.txt is still in the todo branch, but not in the actual main git branch. I assume that this means you were planning on including the v1.5.0.txt in the git announcement, but not necessarily including it in the actual git 1.5.0 tarball?

As a suggestion, maybe it would be a good idea to actually include it as RELEASE-NOTES in the top-level source tree of git. This will make it much more likely that people packaging git will include in /usr/share/doc/git.

Or better yet, maybe we should include it in the Documentation directory and set it up to be built as a manpage, git-release-notes. This will make it much more likely that end users who are getting git from their Fedora, Debian, Red Hat, et. al distribution will actually see the release notes when they install the new package.

What do you think?
						- Ted
Next: Junio C Hamano
Message 1 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.