From: Jakub Narebski <jnareb@gmail.com>
To: Jonas Fonseca <fonseca@diku.dk>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig-0.10
Date: Mon, 17 Mar 2008 02:45:11 -0700 (PDT) [thread overview]
Message-ID: <m3r6e9wup2.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080317020304.GA19249@diku.dk>
Jonas Fonseca <fonseca@diku.dk> writes:
> A new version of tig is available! It brings many documentation
> improvements, bug fixes, and some much needed updates to work better
> with git (e.g. by using --no-color and avoiding to use git-diff).
It seems like 'g', toggle revision graph visualization, doesn't work.
Checked with
$ tig log --pretty=oneline --abbrev=8 --abbrev-commit
> On startup, tig will now attempt to first read a system-wide configuration
> file before loading the user specific configuration file. Cherry picking
> from inside tig has been generalized, making it possible to wire
> external commands, which can access information about the current
> commit, to a keybinding.
By thw ay, in tig(1), in the "FILES" section, there is
/home/fonseca/etc/tigrc
System wide configuration file.
Is it a bug in code, or just in documentation.
tig was installed using:
$ rpmbuild -tb tig-0.10.tar.gz
# rpm -Uhv tig-0.10-0.i386.rpm
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-03-17 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 2:03 [ANNOUNCE] tig-0.10 Jonas Fonseca
2008-03-17 8:25 ` Junio C Hamano
2008-03-17 10:23 ` Jonas Fonseca
2008-03-17 10:49 ` Junio C Hamano
2008-03-17 11:28 ` Jonas Fonseca
2008-03-17 9:45 ` Jakub Narebski [this message]
2008-03-17 10:27 ` Jonas Fonseca
2008-03-19 23:33 ` [ANNOUNCE] tig-0.10.1 Jonas Fonseca
2008-03-20 0:52 ` Junio C Hamano
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=m3r6e9wup2.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.