{"thread":{"id":"31506","subject":"[ANNOUNCE] Git v1.7.11.6","startedAt":"2012-09-11T19:54:02Z","lastAt":"2012-09-11T19:54:02Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"198809","messageId":"7v8vcggwth.fsf@alter.siamese.dyndns.org","threadId":"31506","inReplyTo":null,"subject":"[ANNOUNCE] Git v1.7.11.6","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-11T19:54:02Z","receivedAt":"2012-09-11T19:54:02Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"A maintenance release Git v1.7.11.6 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\nf678531535643806733e8c7e87db77386c48738b  git-1.7.11.6.tar.gz\ne6ccf6cffa3b69dc5d658f43bb8a10ed70b176f2  git-htmldocs-1.7.11.6.tar.gz\n7bbb12429e65184d9462dfc01b104a4780bc67a8  git-manpages-1.7.11.6.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.11.6\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\n[repo seems to be having a problem right now]\n\nGit v1.7.11.6 Release Notes\n===========================\n\nFixes since v1.7.11.5\n---------------------\n\n * \"ciabot\" script (in contrib/) has been updated with extensive\n   documentation.\n\n * \"git foo\" errored out with \"Not a directory\" when the user had a\n   non-directory on $PATH, and worse yet it masked an alias \"foo\" from\n   running.\n\n * When the user exports a non-default IFS without HT, scripts that\n   rely on being able to parse \"ls-files -s | while read a b c...\"\n   started to fail.  Protect them from such a misconfiguration.\n\n * When the user gives an argument that can be taken as both a\n   revision name and a pathname without disambiguating with \"--\", we\n   used to give a help message \"Use '--' to separate\".  The message\n   has been clarified to show where that '--' goes on the command\n   line.\n\n * Documentation for the configuration file format had a confusing\n   example.\n\n * Older parts of the documentation described as if having a regular\n   file in .git/refs/ hierarchy were the only way to have branches and\n   tags, which is not true for quite some time.\n\n * It was generally understood that \"--long-option\"s to many of our\n   subcommands can be abbreviated to the unique prefix, but it was not\n   easy to find it described for new readers of the documentation set.\n\n * The \"--topo-order\", \"--date-order\" (and the lack of either means\n   the default order) options to \"rev-list\" and \"log\" family of\n   commands were poorly described in the documentation.\n\n * \"git commit --amend\" let the user edit the log message and then\n   died when the human-readable committer name was given\n   insufficiently by getpwent(3).\n\n * The exit status code from \"git config\" was way overspecified while\n   being incorrect.  The implementation has been updated to give the\n   documented status for a case that was documented, and introduce a\n   new code for \"all other errors\".\n\n * The output from \"git diff -B\" for a file that ends with an\n   incomplete line did not put \"\\ No newline...\" on a line of its own.\n\n * \"git diff\" had a confusion between taking data from a path in the\n   working tree and taking data from an object that happens to have\n   name 0{40} recorded in a tree.\n\n * The \"--rebase\" option to \"git pull\" can be abbreviated to \"-r\",\n   but we didn't document it.\n\n * When \"git push\" triggered the automatic gc on the receiving end, a\n   message from \"git prune\" that said it was removing cruft leaked to\n   the standard output, breaking the communication protocol.\n\n * The reflog entries left by \"git rebase\" and \"git rebase -i\" were\n   inconsistent (the interactive one gave an abbreviated object name).\n\n * \"git send-email\" did not unquote encoded words that appear on the\n   header correctly, and lost \"_\" from strings.\n\n * \"git stash apply/pop\" did not trigger \"rerere\" upon conflicts\n   unlike other mergy operations.\n\n * \"git submodule <cmd> path\" did not error out when the path to the\n   submodule was misspelt.\n\n * \"git submodule update -f\" did not update paths in the working tree\n   that has local changes.\n   (merge 01d4721 sz/submodule-force-update later to maint).\n\n * \"gitweb\" when used with PATH_INFO failed to notice directories with\n   SP (and other characters that need URL-style quoting) in them.\n\n * Fallback 'getpass' implementation made unportable use of stdio API.\n\n * A utility shell function test_seq has been added as a replacement\n   for the 'seq' utility found on some platforms.\n\n----------------------------------------------------------------\n\nChanges since v1.7.11.5 are as follows:\n\nAdam Butcher (1):\n      Fix '\\ No newline...' annotation in rewrite diffs\n\nBen Walton (1):\n      Enable HAVE_DEV_TTY for Solaris\n\nBrandon Casey (1):\n      t/t5400: demonstrate breakage caused by informational message from prune\n\nEric S. Raymond (3):\n      contrib/ciabot: Get ciabot configuration from git variables\n      Improved documentation for the ciabot scripts.\n      Make the ciabot scripts completely self-configuring in the normal case.\n\nHeiko Voigt (2):\n      Let submodule command exit with error status if path does not exist\n      Documentation/CodingGuidelines: spell out more shell guidelines\n\nJay Soffian (1):\n      gitweb: URL-decode $my_url/$my_uri when stripping PATH_INFO\n\nJeff King (6):\n      commit: check committer identity more strictly\n      diff: do not use null sha1 as a sentinel value\n      do not write null sha1s to on-disk index\n      fsck: detect null sha1 in tree entries\n      terminal: seek when switching between reading and writing\n      docs: monospace listings in docbook output\n\nJunio C Hamano (13):\n      config: \"git config baa\" should exit with status 1\n      t7406: fix misleading \"rev-parse --max-count=1 HEAD\"\n      sane_execvp(): ignore non-directory on $PATH\n      Documentation: do not mention .git/refs/* directories\n      receive-pack: do not leak output from auto-gc to standard output\n      sh-setup: protect from exported IFS\n      rev-list docs: clarify --topo-order description\n      gitcli: describe abbreviation of long options\n      git-config doc: unconfuse an example\n      mergetool: style fixes\n      Prepare for 1.7.11.6\n      Almost 1.7.11.6\n      Git 1.7.11.6\n\nLuka Perkov (1):\n      builtin.h: remove unused cmd_<foo> declarations\n\nMartin von Zweigbergk (1):\n      add tests for 'git rebase --keep-empty'\n\nMatthieu Moy (1):\n      setup: clarify error messages for file/revisions ambiguity\n\nMichael Haggerty (1):\n      git-config.txt: fix example\n\nMichael J Gruber (1):\n      rebase -i: use full onto sha1 in reflog\n\nMichał Kiedrowicz (1):\n      tests: Introduce test_seq\n\nMiklos Vajna (1):\n      man: git pull -r is a short for --rebase\n\nNguyễn Thái Ngọc Duy (1):\n      read_index_from: remove bogus errno assignments\n\nPaul Gortmaker (1):\n      apply: delete unused deflate_origlen from patch struct\n\nPhil Hord (2):\n      test: git-stash conflict sets up rerere\n      stash: invoke rerere in case of conflict\n\nStefan Zager (1):\n      Make 'git submodule update --force' always check out submodules.\n\nThomas Rast (3):\n      send-email: improve RFC2047 quote parsing\n      diff_setup_done(): return void\n      merge-recursive: eliminate flush_buffer() in favor of write_in_full()\n"}]}