[ANNOUNCE] GIT 1.5.0.6

From: Junio C Hamano
Date: Wed Mar 28 2007 - 21:13:17 EST


The latest maintenance release GIT 1.5.0.6 is available at the
usual places:

http://www.kernel.org/pub/software/scm/git/

git-1.5.0.6.tar.{gz,bz2} (tarball)
git-htmldocs-1.5.0.6.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.0.6.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.5.0.6-1.$arch.rpm (RPM)

GIT v1.5.0.6 Release Notes
==========================

Fixes since v1.5.0.5
--------------------

* Bugfixes

- a handful small fixes to gitweb.

- build procedure for user-manual is fixed not to require locally
installed stylesheets.

- "git commit $paths" on paths whose earlier contents were
already updated in the index were failing out.

* Documentation

- user-manual has better cross references.

- gitweb installation/deployment procedure is now documented.

----------------------------------------------------------------

Changes since v1.5.0.5 are as follows:

J. Bruce Fields (5):
user-manual: run xsltproc without --nonet option
user-manual: Use def_ instead of ref_ for glossary references.
glossary: stop generating automatically
glossary: clean up cross-references
user-manual: introduce "branch" and "branch head" differently

Jakub Narebski (4):
gitweb: Fix "next" link in commit view
gitweb: Don't escape attributes in CGI.pm HTML methods
gitweb: Fix not marking signoff lines in "log" view
gitweb: Add some installation notes in gitweb/INSTALL

Jeff King (1):
commit: fix pretty-printing of messages with "\nencoding "

Jim Meyering (1):
user-manual.txt: fix a tiny typo.

Johannes Schindelin (1):
t4118: be nice to non-GNU sed

Junio C Hamano (2):
git-commit: "read-tree -m HEAD" is not the right way to read-tree quickly
GIT 1.5.0.6

Li Yang (1):
gitweb: Change to use explicitly function call cgi->escapHTML()

Michael S. Tsirkin (1):
fix typo in git-am manpage

Peter Eriksen (1):
Documentation/pack-format.txt: Clear up description of types.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/