{"thread":{"id":"33765","subject":"[ANNOUNCE] Git v1.8.2.3","startedAt":"2013-05-09T21:53:00Z","lastAt":"2013-05-09T21:53:00Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"216820","messageId":"7v4neb95xf.fsf@alter.siamese.dyndns.org","threadId":"33765","inReplyTo":null,"subject":"[ANNOUNCE] Git v1.8.2.3","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-09T21:53:00Z","receivedAt":"2013-05-09T21:53:00Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest maintenance release Git v1.8.2.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\n2831f7deec472db4d0d0cdffb4d82d91cecdf295  git-1.8.2.3.tar.gz\nb8d6b3c4077d37b34bf08b6eb53c4ee5901fa2f9  git-htmldocs-1.8.2.3.tar.gz\neb04a2540ff9998e0887a4b862641ac1db723f3e  git-manpages-1.8.2.3.tar.gz\n\nAlso the following public repositories all have a copy of the v1.8.2.3\ntag and the maint branch that the tag points at:\n\n  url = https://kernel.googlesource.com/pub/scm/git/git\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\nThe original tarball location\n\n    http://www.kernel.org/pub/software/scm/git/\n\nwill also have the source tarball, but not the preformatted\ndocumentation tarballs.\n\n\nGit v1.8.2.3 Release Notes\n==========================\n\nFixes since v1.8.2.2\n--------------------\n\n * \"rev-list --stdin\" and friends kept bogus pointers into the input\n   buffer around as human readable object names.  This was not a\n   huge problem but was exposed by a new change that uses these\n   names in error output.\n\n * When \"git difftool\" drove \"kdiff3\", it mistakenly passed --auto\n   option that was meant while resolving merge conflicts.\n\n * \"git remote add\" command did not diagnose extra command line\n   arguments as an error and silently ignored them.\n\nAlso contains a handful of trivial code clean-ups, documentation\nupdates, updates to the test suite, etc.\n\n----------------------------------------------------------------\n\nChanges since v1.8.2.2 are as follows:\n\nAnders Granskogen Bjørnstad (1):\n      Documentation/git-commit: Typo under --edit\n\nDavid Aguilar (1):\n      mergetools/kdiff3: do not use --auto when diffing\n\nFelipe Contreras (5):\n      documentation: trivial whitespace cleanups\n      complete: zsh: trivial simplification\n      complete: zsh: use zsh completion for the main cmd\n      completion: zsh: don't override suffix on _detault\n      transport-helper: trivial style cleanup\n\nJohn Keeping (1):\n      t/Makefile: remove smoke test targets\n\nJonathan Nieder (1):\n      glossary: a revision is just a commit\n\nJunio C Hamano (1):\n      Git 1.8.2.3\n\nRamkumar Ramachandra (3):\n      git-completion.bash: lexical sorting for diff.statGraphWidth\n      git-completion.bash: add diff.submodule to config list\n      git-completion.bash: complete branch.*.rebase as boolean\n\nRené Scharfe (2):\n      t5004: ignore pax global header file\n      t5004: avoid using tar for checking emptiness of archive\n\nThomas Rast (4):\n      read_revisions_from_stdin: make copies for handle_revision_arg\n      remote: add a test for extra arguments, according to docs\n      remote: check for superfluous arguments in 'git remote add'\n      remote: 'show' and 'prune' can take more than one remote\n"}]}