From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git v1.8.4.5
Date: Tue, 03 Dec 2013 13:48:11 -0800 [thread overview]
Message-ID: <xmqq38m9mwlr.fsf@gitster.dls.corp.google.com> (raw)
A maintenance release Git v1.8.4.5 is now available at the
usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
b43c0cc46749ad62b8ac74237ceca00c8e386edb git-1.8.4.5.tar.gz
bd66db8c9528e53d2b93e88ef8e96164e597333f git-htmldocs-1.8.4.5.tar.gz
1ff6380e60c879a563ef89452ca461e9610e41c0 git-manpages-1.8.4.5.tar.gz
The following public repositories all have a copy of the v1.8.4.5
tag and the maint-1.8.4 branch that the tag points at:
url = https://kernel.googlesource.com/pub/scm/git/git
url = git://repo.or.cz/alt-git.git
url = https://code.google.com/p/git-core/
url = git://git.sourceforge.jp/gitroot/git-core/git.git
url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core
url = https://github.com/gitster/git
Also, http://www.kernel.org/pub/software/scm/git/ has copies of the
release tarballs.
Git v1.8.4.5 Release Notes
==========================
Fixes since v1.8.4.4
--------------------
* Recent update to remote-hg that attempted to make it work better
with non ASCII pathnames fed Unicode strings to the underlying Hg
API, which was wrong.
* "git submodule init" copied "submodule.$name.update" settings from
.gitmodules to .git/config without making sure if the suggested
value was sensible.
----------------------------------------------------------------
Changes since v1.8.4.4 are as follows:
Junio C Hamano (2):
submodule: do not copy unknown update mode from .gitmodules
Git 1.8.4.5
Richard Hansen (1):
remote-hg: don't decode UTF-8 paths into Unicode objects
reply other threads:[~2013-12-03 21:52 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=xmqq38m9mwlr.fsf@gitster.dls.corp.google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.