From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git v1.8.2.3
Date: Thu, 09 May 2013 14:53:00 -0700 [thread overview]
Message-ID: <7v4neb95xf.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git v1.8.2.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:
2831f7deec472db4d0d0cdffb4d82d91cecdf295 git-1.8.2.3.tar.gz
b8d6b3c4077d37b34bf08b6eb53c4ee5901fa2f9 git-htmldocs-1.8.2.3.tar.gz
eb04a2540ff9998e0887a4b862641ac1db723f3e git-manpages-1.8.2.3.tar.gz
Also the following public repositories all have a copy of the v1.8.2.3
tag and the maint branch that the tag points at:
url = https://kernel.googlesource.com/pub/scm/git/git
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
The original tarball location
http://www.kernel.org/pub/software/scm/git/
will also have the source tarball, but not the preformatted
documentation tarballs.
Git v1.8.2.3 Release Notes
==========================
Fixes since v1.8.2.2
--------------------
* "rev-list --stdin" and friends kept bogus pointers into the input
buffer around as human readable object names. This was not a
huge problem but was exposed by a new change that uses these
names in error output.
* When "git difftool" drove "kdiff3", it mistakenly passed --auto
option that was meant while resolving merge conflicts.
* "git remote add" command did not diagnose extra command line
arguments as an error and silently ignored them.
Also contains a handful of trivial code clean-ups, documentation
updates, updates to the test suite, etc.
----------------------------------------------------------------
Changes since v1.8.2.2 are as follows:
Anders Granskogen Bjørnstad (1):
Documentation/git-commit: Typo under --edit
David Aguilar (1):
mergetools/kdiff3: do not use --auto when diffing
Felipe Contreras (5):
documentation: trivial whitespace cleanups
complete: zsh: trivial simplification
complete: zsh: use zsh completion for the main cmd
completion: zsh: don't override suffix on _detault
transport-helper: trivial style cleanup
John Keeping (1):
t/Makefile: remove smoke test targets
Jonathan Nieder (1):
glossary: a revision is just a commit
Junio C Hamano (1):
Git 1.8.2.3
Ramkumar Ramachandra (3):
git-completion.bash: lexical sorting for diff.statGraphWidth
git-completion.bash: add diff.submodule to config list
git-completion.bash: complete branch.*.rebase as boolean
René Scharfe (2):
t5004: ignore pax global header file
t5004: avoid using tar for checking emptiness of archive
Thomas Rast (4):
read_revisions_from_stdin: make copies for handle_revision_arg
remote: add a test for extra arguments, according to docs
remote: check for superfluous arguments in 'git remote add'
remote: 'show' and 'prune' can take more than one remote
reply other threads:[~2013-05-09 21:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v4neb95xf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox