From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] GIT 1.6.0.6
Date: Fri, 19 Dec 2008 22:40:41 -0800 [thread overview]
Message-ID: <7vljub1h92.fsf@gitster.siamese.dyndns.org> (raw)
The latest maintenance release GIT 1.6.0.6 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.6.0.6.tar.{gz,bz2} (source tarball)
git-htmldocs-1.6.0.6.tar.{gz,bz2} (preformatted docs)
git-manpages-1.6.0.6.tar.{gz,bz2} (preformatted docs)
The RPM binary packages for a few architectures are also provided
as courtesy.
RPMS/$arch/git-*-1.6.0.6-1.fc9.$arch.rpm (RPM)
Among miscellaneous fixes, this contains a local gitweb security fix.
Maintenance releases for older versions (v1.5.4.7, v1.5.5.6 and v1.5.6.6)
are also available at the same place.
----------------------------------------------------------------
Changes since v1.6.0.5 are as follows:
David Aguilar (1):
git-mergetool: properly handle "git mergetool -- filename"
Deskin Miller (1):
git-svn: Make following parents atomic
Jim Meyering (1):
git-config.txt: fix a typo
Johannes Schindelin (2):
fast-import: close pack before unlinking it
fast-export: deal with tag objects that do not have a tagger
Junio C Hamano (6):
work around Python warnings from AsciiDoc
git-show: do not segfault when showing a bad tag
pager: do not dup2 stderr if it is already redirected
gitweb: do not run "git diff" that is Porcelain
GIT 1.5.4.7
fast-import: make tagger information optional
Linus Torvalds (1):
fsck: reduce stack footprint
Markus Heidelberg (1):
Documentation: fix typos, grammar, asciidoc syntax
Miklos Vajna (1):
SubmittingPatches: mention the usage of real name in Signed-off-by: lines
Nicolas Pitre (1):
make sure packs to be replaced are closed beforehand
Wu Fengguang (1):
git-send-email: handle email address with quoted comma
next reply other threads:[~2008-12-20 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 6:40 Junio C Hamano [this message]
2008-12-20 6:46 ` [Security] gitweb local privilege escalation (fix) Junio C Hamano
2008-12-20 10:54 ` Jakub Narebski
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=7vljub1h92.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;
as well as URLs for NNTP newsgroup(s).