From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git 1.6.5.7
Date: Wed, 16 Dec 2009 16:29:14 -0800 [thread overview]
Message-ID: <7vfx7aqw85.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git 1.6.5.7 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.5.7.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.5.7.tar.{gz,bz2} (preformatted docs)
git-manpages-1.6.5.7.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are found in:
RPMS/$arch/git-*-1.6.5.7-1.fc11.$arch.rpm (RPM)
Nothing spectacular to see here, but as I was tagging 1.6.6-rc3 today, I
wanted to push out fixes accumulated on the maintenance branch in a tagged
release. Everything in this release is also in 1.6.6-rc3.
----------------------------------------------------------------
Changes since v1.6.5.6 are as follows:
Jeff King (1):
ignore unknown color configuration
Johannes Sixt (1):
help.autocorrect: do not run a command if the command given is junk
Junio C Hamano (2):
worktree: don't segfault with an absolute pathspec without a work tree
Git 1.6.5.7
Nanako Shiraishi (1):
Illustrate "filter" attribute with an example
reply other threads:[~2009-12-17 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7vfx7aqw85.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@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