threads / announce / 31757

[ANNOUNCE] Git v1.7.12.3

Subject: [ANNOUNCE] Git v1.7.12.3

## tl;dr

One message between Oct 8, 2012 and Oct 8, 2012.

replies: 0people: 1as markdown or json

Junio C Hamano· Oct 8, 2012, 19:53 UTC · lore

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

← back to recent threads