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
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?