From: Jonas Fonseca <fonseca@diku.dk>
To: git@vger.kernel.org
Subject: [ANNOUNCE] tig 0.5
Date: Mon, 25 Sep 2006 01:31:12 +0200 [thread overview]
Message-ID: <20060924233112.GB695@diku.dk> (raw)
Hello,
After a long break a few changes have started to accumulate so here is
version 0.5 of tig. It adds some basic features like searching and
support for keybindings (see tigrc(5)). Additionally, It fixes most of
the things I would have hoped to include in this release. I tried to fix
the problems reported with terminal encoding by using iconv, but earlier
tonight I found that it needs some more work.
Looking forward, better input support is much desired, plus I'd like to
review the drawing code to see if it can be optimized to do fewer
updates. Also, a blame view is in the pipeline and I have a proof of
concept implementation of revision graph rendering (it is available in
the new/rev-graph branch).
A list of tig resources:
- Homepage: http://jonas.nitro.dk/tig/
- Releases: http://jonas.nitro.dk/tig/releases/
- Git URL: http://jonas.nitro.dk/tig/tig.git or
git://repo.or.cz/tig.git
- Gitweb: http://repo.or.cz/?p=tig.git;a=summary
Tarballs contain all the generated documentation, as do the #release
branch of the git repository.
--
Jonas Fonseca
reply other threads:[~2006-09-24 23:31 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=20060924233112.GB695@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