From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git 1.7.8.3
Date: Fri, 06 Jan 2012 13:53:53 -0800 [thread overview]
Message-ID: <7vsjjsijke.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git 1.7.8.3 is available.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
e5eb8c289b69d69fd08c81b587a06eb5dd2b5c1c git-1.7.8.3.tar.gz
8a65d2425c1b6f646d130cf5846e92e9e0e93736 git-htmldocs-1.7.8.3.tar.gz
a6e2b7cff8181ee52a1cc00ebba7b349850d6680 git-manpages-1.7.8.3.tar.gz
Also the following public repositories all have a copy of the v1.7.8.3
tag and the maint branch that the tag points at:
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
----------------------------------------------------------------
Changes since v1.7.8.2 are as follows:
Brian Harring (1):
fix hang in git fetch if pointed at a 0 length bundle
Clemens Buchacher (2):
Documentation: read-tree --prefix works with existing subtrees
t5550: repack everything into one file
Jack Nagel (1):
Add MYMETA.json to perl/.gitignore
Jakub Narebski (1):
gitweb: Fix fallback mode of to_utf8 subroutine
Jens Lehmann (1):
docs: describe behavior of relative submodule URLs
Junio C Hamano (1):
Git 1.7.8.3
Jürgen Kreileder (3):
gitweb: Call to_utf8() on input string in chop_and_escape_str()
gitweb: esc_html() site name for title in OPML
gitweb: Output valid utf8 in git_blame_common('data')
Nguyễn Thái Ngọc Duy (1):
Catch invalid --depth option passed to clone or fetch
Thomas Rast (1):
Documentation: rerere.enabled is the primary way to configure rerere
reply other threads:[~2012-01-06 21:54 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=7vsjjsijke.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