From: Jonas Fonseca <fonseca@diku.dk>
To: git@vger.kernel.org
Subject: [ANNOUNCE] tig-0.13
Date: Wed, 14 Jan 2009 00:36:43 +0100 [thread overview]
Message-ID: <20090113233643.GA28898@diku.dk> (raw)
Hello,
This release contains a major rewrite of the IO layer of tig to use
fork+exec instead of popen() and remove use of stdio's fopen() and
friends. The new IO API removes the need for shell quoting and improves
the overall speed of loading view data. On the downside, it brings a few
incompatibilities wrt. commands given via the environment. While the
patch series began by being based on git's run-command.c module, the
final version contains no code from git.
The release also brings a few new features, such as new identifiers for
use in external commands as well as a handful of bug fixes.
What is tig?
------------
Tig is an ncurses-based text-mode interface for git. It functions mainly
as a git repository browser, but can also assist in staging changes for
commit at chunk level and act as a pager for output from various git
commands.
- Homepage: http://jonas.nitro.dk/tig/
- Manual: http://jonas.nitro.dk/tig/manual.html
- Tarballs: http://jonas.nitro.dk/tig/releases/
- Git URL: git://repo.or.cz/tig.git
- Gitweb: http://repo.or.cz/w/tig.git
Release notes
-------------
Incompatibilities:
- Commands from the environment (e.g. TIG_MAIN_CMD) will no longer have
access to shell features, such as subshells and variable expansion.
The easiest way to upgrade your configuration is to put such commands
in a script file.
Improvements:
- Display repository references in the sorted order: tags, heads,
tracked remotes, remotes.
- Add bash completion for blame.
- Tree view: edit files of the current branch.
- Run requests: new identifiers %(directory), %(file), and %(ref)
- Improve responsiveness and view loading speed by using select(2).
Bug fixes:
- Separate blame revision and file argument by "--" to avoid problems.
- Main view: fix redrawing of the last commit wrt. the revision graph.
- Fix waiting for input after executing a run request in pager mode.
- Status & stage view: refuse to open directories and deleted files.
- Tree view: show error when requesting blame for all non-file entries.
- Do not draw loading views, which are not displayed.
- Fix launching of mergetool from a subdirectory.
Change summary
--------------
The diffstat and log summary for changes made in this release.
NEWS | 29 +
VERSION | 2 +-
contrib/announcement.sh | 2 +-
contrib/tig-completion.bash | 25 +-
manual.txt | 281 ++++---
tig.1.txt | 6 +-
tig.c | 1774 +++++++++++++++++++++--------------
tigrc.5.txt | 23 +-
8 files changed, 1325 insertions(+), 817 deletions(-)
53 Jonas Fonseca
--
Jonas Fonseca
next reply other threads:[~2009-01-13 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 23:36 Jonas Fonseca [this message]
2009-01-14 16:33 ` [ANNOUNCE] tig-0.13 Ted Pavlic
2009-01-14 23:24 ` bill lam
2009-01-14 23:56 ` Jonas Fonseca
2009-01-15 1:46 ` bill lam
2009-01-15 13:06 ` Jonas Fonseca
2009-01-15 14:50 ` bill lam
2009-01-15 15:05 ` Adeodato Simó
2009-01-15 15:08 ` Jonas Fonseca
2009-01-15 15:41 ` bill lam
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=20090113233643.GA28898@diku.dk \
--to=fonseca@diku.dk \
--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).