From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git v1.7.12.3
Date: Mon, 08 Oct 2012 12:53:23 -0700 [thread overview]
Message-ID: <7vmwzwk9le.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git v1.7.12.3 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:
a071f03f6aab76b283828db1fdedbedb90085eb5 git-1.7.12.3.tar.gz
6f976c27aab7250f1a35b2b002ac7a07c3266cf4 git-htmldocs-1.7.12.3.tar.gz
49584f0b72e4a13f9a4df771bbde9cf70f25d317 git-manpages-1.7.12.3.tar.gz
Also the following public repositories all have a copy of the v1.7.12.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
Git 1.7.12.3 Release Notes
==========================
Fixes since v1.7.12.2
---------------------
* "git am" mishandled a patch attached as application/octet-stream
(e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not
honored correctly.
* It was unclear in the documentation for "git blame" that it is
unnecessary for users to use the "--follow" option.
* A repository created with "git clone --single" had its fetch
refspecs set up just like a clone without "--single", leading the
subsequent "git fetch" to slurp all the other branches, defeating
the whole point of specifying "only this branch".
* "git fetch" over http had an old workaround for an unlikely server
misconfiguration; it turns out that this hurts debuggability of the
configuration in general, and has been reverted.
* "git fetch" over http advertised that it supports "deflate", which
is much less common, and did not advertise the more common "gzip" on
its Accept-Encoding header.
* "git receive-pack" (the counterpart to "git push") did not give
progress output while processing objects it received to the puser
when run over the smart-http protocol.
* "git status" honored the ignore=dirty settings in .gitmodules but
"git commit" didn't.
Also contains a handful of documentation updates.
----------------------------------------------------------------
Changes since v1.7.12.2 are as follows:
Jeff King (3):
receive-pack: redirect unpack-objects stdout to /dev/null
receive-pack: send pack-processing stderr over sideband
receive-pack: drop "n/a" on unpacker errors
Junio C Hamano (3):
git blame: document that it always follows origin across whole-file renames
Start preparing for 1.7.12.3
Git 1.7.12.3
Linus Torvalds (1):
mailinfo: don't require "text" mime type for attachments
Orgad Shaneh (1):
commit: pay attention to submodule.$name.ignore in .gitmodules
Peter Krefting (1):
l10n: Fix to Swedish translation
Ralf Thielow (1):
clone --single: limit the fetch refspec to fetched branch
Ramkumar Ramachandra (1):
submodule: if $command was not matched, don't parse other args
Shawn O. Pearce (2):
Revert "retry request without query when info/refs?query fails"
Enable info/refs gzip decompression in HTTP client
reply other threads:[~2012-10-08 20:11 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmwzwk9le.fsf@alter.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).