From: Jakub Narebski <jnareb@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Thu, 15 Feb 2007 02:55:10 +0100 [thread overview]
Message-ID: <er0eee$6qp$1@sea.gmane.org> (raw)
In-Reply-To: 7vlkj1v3av.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> - git-blame learned a new option, --incremental, that tells it
> to output the blames as they are assigned. A sample script
> to use it is also included as contrib/blameview.
And there are example GUI blameview (Perk GTK2), and example Emacs module
for incremental git-blame, both in contib/ area.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0
Date: Thu, 15 Feb 2007 02:55:10 +0100 [thread overview]
Message-ID: <er0eee$6qp$1@sea.gmane.org> (raw)
In-Reply-To: 7vlkj1v3av.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> - git-blame learned a new option, --incremental, that tells it
> to output the blames as they are assigned. A sample script
> to use it is also included as contrib/blameview.
And there are example GUI blameview (Perk GTK2), and example Emacs module
for incremental git-blame, both in contib/ area.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-15 1:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 3:14 [ANNOUNCE] GIT 1.5.0 Junio C Hamano
2007-02-14 9:06 ` Andy Parkins
2007-02-14 9:35 ` Junio C Hamano
2007-02-14 9:48 ` Junio C Hamano
2007-02-14 12:42 ` Matthieu Moy
2007-02-14 14:57 ` Bill Lear
2007-02-14 16:45 ` Linus Torvalds
2007-02-15 1:55 ` Jakub Narebski [this message]
2007-02-15 1:55 ` Jakub Narebski
2007-02-15 2:11 ` Shawn O. Pearce
2007-02-16 22:31 ` A note from the maintainer Junio C Hamano
2007-02-17 2:35 ` Johannes Schindelin
2007-02-23 6:03 ` 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='er0eee$6qp$1@sea.gmane.org' \
--to=jnareb@gmail.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 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.