From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Git v2.3.6
Date: Tue, 21 Apr 2015 14:53:24 -0700 [thread overview]
Message-ID: <xmqqsibtf8rv.fsf@gitster.dls.corp.google.com> (raw)
The latest maintenance release Git v2.3.6 is now available at the
usual places. It is comprised of 14 non-merge commits since v2.3.5,
contributed by 8 people, 4 of which are new faces.
There is not much to see there (the changes are mostly documentation
and test updates), except for updates to diff-highlight in contrib/.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.3.6'
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
New contributors whose contributions weren't in v2.3.5 are as follows.
Welcome to the Git development community!
Ivan Ukhov, Jérôme Zago, Julian Gindi, and Paul Tan.
Returning contributors who helped this release are as follows.
Thanks for your continued support.
Jeff King, Jonathan Nieder, Junio C Hamano, and Kyle J. McKay.
----------------------------------------------------------------
Git v2.3.6 Release Notes
========================
Fixes since v2.3.5
------------------
* "diff-highlight" (in contrib/) used to show byte-by-byte
differences, which meant that multi-byte characters can be chopped
in the middle. It learned to pay attention to character boundaries
(assuming the UTF-8 payload).
Also contains typofixes, documentation updates and trivial code
clean-ups.
----------------------------------------------------------------
Changes since v2.3.5 are as follows:
Ivan Ukhov (1):
parse-options.h: OPTION_{BIT,SET_INT} do not store pointer to defval
Jeff King (7):
t: translate SIGINT to an exit
t: redirect stderr GIT_TRACE to descriptor 4
t: pass GIT_TRACE through Apache
t5541: move run_with_cmdline_limit to test-lib.sh
t5551: make EXPENSIVE test cheaper
cherry-pick: fix docs describing handling of empty commits
howto: document more tools for recovery corruption
Jonathan Nieder (1):
fast-import doc: remove suggested 16-parent limit
Julian Gindi (1):
CodingGuidelines: update 'rough' rule count
Junio C Hamano (1):
Git 2.3.6
Jérôme Zago (1):
gitweb.conf.txt: say "build-time", not "built-time"
Kyle J. McKay (1):
diff-highlight: do not split multibyte characters
Paul Tan (1):
enter_repo(): fix docs to match code
reply other threads:[~2015-04-21 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=xmqqsibtf8rv.fsf@gitster.dls.corp.google.com \
--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