{"thread":{"id":"31757","subject":"[ANNOUNCE] Git v1.7.12.3","startedAt":"2012-10-08T19:53:23Z","lastAt":"2012-10-08T19:53:23Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"200783","messageId":"7vmwzwk9le.fsf@alter.siamese.dyndns.org","threadId":"31757","inReplyTo":null,"subject":"[ANNOUNCE] Git v1.7.12.3","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-10-08T19:53:23Z","receivedAt":"2012-10-08T19:53:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git v1.7.12.3 is now available at\nthe usual places.\n\nThe release tarballs are found at:\n\n    http://code.google.com/p/git-core/downloads/list\n\nand their SHA-1 checksums are:\n\na071f03f6aab76b283828db1fdedbedb90085eb5  git-1.7.12.3.tar.gz\n6f976c27aab7250f1a35b2b002ac7a07c3266cf4  git-htmldocs-1.7.12.3.tar.gz\n49584f0b72e4a13f9a4df771bbde9cf70f25d317  git-manpages-1.7.12.3.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.12.3\ntag and the maint branch that the tag points at:\n\n  url = git://repo.or.cz/alt-git.git\n  url = https://code.google.com/p/git-core/\n  url = git://git.sourceforge.jp/gitroot/git-core/git.git\n  url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n  url = https://github.com/gitster/git\n\nGit 1.7.12.3 Release Notes\n==========================\n\nFixes since v1.7.12.2\n---------------------\n\n * \"git am\" mishandled a patch attached as application/octet-stream\n   (e.g. not text/*); Content-Transfer-Encoding (e.g. base64) was not\n   honored correctly.\n\n * It was unclear in the documentation for \"git blame\" that it is\n   unnecessary for users to use the \"--follow\" option.\n\n * A repository created with \"git clone --single\" had its fetch\n   refspecs set up just like a clone without \"--single\", leading the\n   subsequent \"git fetch\" to slurp all the other branches, defeating\n   the whole point of specifying \"only this branch\".\n\n * \"git fetch\" over http had an old workaround for an unlikely server\n   misconfiguration; it turns out that this hurts debuggability of the\n   configuration in general, and has been reverted.\n\n * \"git fetch\" over http advertised that it supports \"deflate\", which\n   is much less common, and did not advertise the more common \"gzip\" on\n   its Accept-Encoding header.\n\n * \"git receive-pack\" (the counterpart to \"git push\") did not give\n   progress output while processing objects it received to the puser\n   when run over the smart-http protocol.\n\n * \"git status\" honored the ignore=dirty settings in .gitmodules but\n   \"git commit\" didn't.\n\nAlso contains a handful of documentation updates.\n\n----------------------------------------------------------------\n\nChanges since v1.7.12.2 are as follows:\n\nJeff King (3):\n      receive-pack: redirect unpack-objects stdout to /dev/null\n      receive-pack: send pack-processing stderr over sideband\n      receive-pack: drop \"n/a\" on unpacker errors\n\nJunio C Hamano (3):\n      git blame: document that it always follows origin across whole-file renames\n      Start preparing for 1.7.12.3\n      Git 1.7.12.3\n\nLinus Torvalds (1):\n      mailinfo: don't require \"text\" mime type for attachments\n\nOrgad Shaneh (1):\n      commit: pay attention to submodule.$name.ignore in .gitmodules\n\nPeter Krefting (1):\n      l10n: Fix to Swedish translation\n\nRalf Thielow (1):\n      clone --single: limit the fetch refspec to fetched branch\n\nRamkumar Ramachandra (1):\n      submodule: if $command was not matched, don't parse other args\n\nShawn O. Pearce (2):\n      Revert \"retry request without query when info/refs?query fails\"\n      Enable info/refs gzip decompression in HTTP client\n"}]}