From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git 1.7.10.4
Date: Sun, 03 Jun 2012 16:48:29 -0700 [thread overview]
Message-ID: <7vvcj8ueej.fsf@alter.siamese.dyndns.org> (raw)
The latest maintenance release Git v1.7.10.4 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:
ddc305ab520246790faa72bbaab4b9bf5bcf23fa git-1.7.10.4.tar.gz
951ecda5cbc3e7a5f30b419506ec24b54afa2b93 git-htmldocs-1.7.10.4.tar.gz
0769f6ff48d89df908cfe2af85fb4072b4178746 git-manpages-1.7.10.4.tar.gz
Also the following public repositories all have a copy of the v1.7.10.4
tag and the maint branch that the tag points at:
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
Git v1.7.10.4 Release Notes
===========================
Fixes since v1.7.10.3
---------------------
* The message file for Swedish translation has been updated a bit.
* A name taken from mailmap was copied into an internal buffer
incorrectly and could overun the buffer if it is too long.
* A malformed commit object that has a header line chomped in the
middle could kill git with a NULL pointer dereference.
* An author/committer name that is a single character was mishandled
as an invalid name by mistake.
* The progress indicator for a large "git checkout" was sent to
stderr even if it is not a terminal.
* "git grep -e '$pattern'", unlike the case where the patterns are
read from a file, did not treat individual lines in the given
pattern argument as separate regular expressions as it should.
* When "git rebase" was given a bad commit to replay the history on,
its error message did not correctly give the command line argument
it had trouble parsing.
Also contains minor fixes and documentation updates.
----------------------------------------------------------------
Changes since v1.7.10.3 are as follows:
Avery Pennarun (1):
checkout: no progress messages if !isatty(2).
Erik Faye-Lund (2):
rebase: report invalid commit correctly
Makefile: add missing GIT-VERSION-FILE dependency
Jeff King (3):
fix off-by-one error in split_ident_line
pretty: avoid buffer overflow in format_person_part
avoid segfault when reading header of malformed commits
Junio C Hamano (2):
Start preparing for 1.7.10.4
Git 1.7.10.4
Peter Krefting (1):
Update Swedish translation (728t0f0u)
René Scharfe (4):
grep: factor out create_grep_pat()
grep: factor out do_append_grep_pat()
grep: support newline separated pattern list
grep: stop leaking line strings with -f
reply other threads:[~2012-06-04 0:09 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=7vvcj8ueej.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
all inboxes | Powered by JetHome®