From: Jonas Fonseca <jonas.fonseca@gmail.com>
To: git <git@vger.kernel.org>
Subject: [ANNOUNCE] tig-2.3.3
Date: Tue, 30 Jan 2018 20:47:50 -0500 [thread overview]
Message-ID: <CAFuPQ1L7AKp5UXzLxUhFWkmK2HPRZhOMbapqdT7bCpbHSHkUow@mail.gmail.com> (raw)
Hello,
A regression in 2.3.1 (and 2.3.2) related with the detection of busy loops has
been revisited in version 2.3.3.
Release notes
-------------
Bug fixes:
- Revert "Handle \n like \r (#758)". (GH #769)
- Fix GH #164 by catching SIGHUP.
- Change `refs_tags` type to `size_t`.
Change summary
--------------
The diffstat and log summary for changes made in this release.
INSTALL.adoc | 4 ++--
Makefile | 2 +-
NEWS.adoc | 9 +++++++++
README.adoc | 2 +-
src/display.c | 40 ----------------------------------------
src/refdb.c | 2 +-
src/tig.c | 12 ++++++++++++
tools/aspell.dict | 2 +-
8 files changed, 27 insertions(+), 46 deletions(-)
Alexander Droste (1):
Revert "Handle \n like \r (#758)" (#769)
Jonas Fonseca (3):
Fix #164 by catching SIGHUP
Change refs_tags type to size_t
tig-2.3.3
harshavardhan (1):
updated https to https (#777)
--
Jonas Fonseca
reply other threads:[~2018-01-31 1:48 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=CAFuPQ1L7AKp5UXzLxUhFWkmK2HPRZhOMbapqdT7bCpbHSHkUow@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).