{"thread":{"id":"31538","subject":"[ANNOUNCE] Git v1.7.11.7","startedAt":"2012-09-15T06:12:10Z","lastAt":"2012-09-15T06:12:10Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"199089","messageId":"7v8vcb24sl.fsf@alter.siamese.dyndns.org","threadId":"31538","inReplyTo":null,"subject":"[ANNOUNCE] Git v1.7.11.7","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-15T06:12:10Z","receivedAt":"2012-09-15T06:12:10Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"A maintenance release Git v1.7.11.7 is now available at the\nusual 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\n30c7aafaa31002ca52bc45dbd0908e63b00015dd  git-1.7.11.7.tar.gz\nbdcd5009498bc961757915dae30f5fefd6435c59  git-htmldocs-1.7.11.7.tar.gz\n9fb4bb051822168e41424524a4a325207f308507  git-manpages-1.7.11.7.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.11.7\ntag and the maint-1.7.11 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 v1.7.11.7 Release Notes\n===========================\n\nFixes since v1.7.11.6\n---------------------\n\n * The synopsis said \"checkout [-B branch]\" to make it clear the\n   branch name is a parameter to the option, but the heading for the\n   option description was \"-B::\", not \"-B branch::\", making the\n   documentation misleading.\n\n * Git ships with a fall-back regexp implementation for platforms with\n   buggy regexp library, but it was easy for people to keep using their\n   platform regexp.  A new test has been added to check this.\n\n * \"git apply -p0\" did not parse pathnames on \"diff --git\" line\n   correctly.  This caused patches that had pathnames in no other\n   places to be mistakenly rejected (most notably, binary patch that\n   does not rename nor change mode).  Textual patches, renames or mode\n   changes have preimage and postimage pathnames in different places\n   in a form that can be parsed unambiguously and did not suffer from\n   this problem.\n\n * After \"gitk\" showed the contents of a tag, neither \"Reread\n   references\" nor \"Reload\" did not update what is shown as the\n   contents of it, when the user overwrote the tag with \"git tag -f\".\n\n * \"git for-each-ref\" did not currectly support more than one --sort\n   option.\n\n * \"git log ..\" errored out saying it is both rev range and a path\n   when there is no disambiguating \"--\" is on the command line.\n   Update the command line parser to interpret \"..\" as a path in such\n   a case.\n\n * Pushing to smart HTTP server with recent Git fails without having\n   the username in the URL to force authentication, if the server is\n   configured to allow GET anonymously, while requiring authentication\n   for POST.\n\n * \"git show --format='%ci'\" did not give timestamp correctly for\n   commits created without human readable name on \"committer\" line.\n   (merge e27ddb6 jc/maint-ident-missing-human-name later to maint).\n\n * \"git show --quiet\" ought to be a synonym for \"git show -s\", but\n   wasn't.\n"}]}