From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.5.4.1
Date: Sun, 10 Feb 2008 02:47:59 -0800 [thread overview]
Message-ID: <7vodapgk9s.fsf@gitster.siamese.dyndns.org> (raw)
The latest maintenance release GIT 1.5.4.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.4.1.tar.{gz,bz2} (tarball)
git-htmldocs-1.5.4.1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.4.1.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.5.4.1-1.$arch.rpm (RPM)
Among a handful of documentation patches, there are a few true
bugfixes.
* An entry in the .gitattributes file that names a pattern in a
subdirectory of the directory it is in did not match
correctly (e.g. pattern "b/*.c" in "a/.gitattributes" should
match "a/b/foo.c" but it didn't).
* "git-commit -C $tag" used to work but rewrite in C done in
1.5.4 broke it, which this release fixes.
* Customized color specification was parsed incorrectly when
numeric color values are used.
----------------------------------------------------------------
Changes since v1.5.4 are as follows:
Gerrit Pape (1):
INSTALL: git-merge no longer uses cpio
Jari Aalto (1):
Documentation/git-stash.txt: Adjust SYNOPSIS command syntax (2)
Junio C Hamano (3):
Update stale documentation links from the main documentation.
Fix "git-commit -C $tag"
gitattributes: fix relative path matching
Jörg Sommer (2):
git-am: fix type in its usage string
git-remote documentation: fix synopsis to match description
Tim Stoakes (1):
Fix typo in 'blame' documentation.
Timo Hirvonen (1):
Fix parsing numeric color values
next reply other threads:[~2008-02-10 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 10:47 Junio C Hamano [this message]
2008-02-17 9:14 ` [ANNOUNCE] GIT 1.5.4.2 Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vodapgk9s.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox