From: Junio C Hamano <junkio@cox•net>
To: git@vger•kernel.org
Cc: Luben Tuikov <ltuikov@yahoo•com>, Petr Baudis <pasky@suse•cz>,
Jakub Narebski <jnareb@gmail•com>,
Ryan Anderson <ryan@michonline•com>,
Johannes Schindelin <Johannes.Schindelin@gmx•de>,
Martin Langhoff <martin@catalyst•net.nz>,
Martyn Smith <martyn@catalyst•net.nz>,
Fredrik Kuivinen <freku045@student•liu.se>,
Linus Torvalds <torvalds@osdl•org>
Subject: perhaps time to remove git_blame from gitweb, and git-annotate?
Date: Thu, 05 Oct 2006 01:13:15 -0700 [thread overview]
Message-ID: <7vu02jfaec.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061005064817.21552.qmail@web31804.mail.mud.yahoo.com> (Luben Tuikov's message of "Wed, 4 Oct 2006 23:48:17 -0700 (PDT)")
It's been a while since we lost git_blame from %actions list. I
am wondering maybe it's time to remove it, after 1.4.3 happens.
While I was looking at it, I noticed that it would make
git-cvsserver the last in-tree user of git-annotate. As I
understand it, "git-blame -c" should produce compatible output
to the command, so it might also be a good time to consider
removal of git-annotate as well while updating git-cvsserver to
use git-blame instead of it.
Do people have reason to favor annotate over blame? To keep
existing people's scripts working I think we should add a small
amount of code to blame.c to default to compatibility mode when
the command is called as git-annotate at least for a while, but
other than that I do not see much issue against scheduling for
annotate's removal.
I am not going to do anything about this right now (the "master"
branch is in freeze-and-stabilize phase), but if people have
issues I overlooked, raise hands now please?
next prev parent reply other threads:[~2006-10-05 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 0:59 [PATCH 1/2] gitweb: blame: Print just a single new line char per table row Luben Tuikov
2006-10-05 2:35 ` Junio C Hamano
2006-10-05 6:48 ` Luben Tuikov
2006-10-05 8:13 ` Junio C Hamano [this message]
2006-10-06 13:07 ` perhaps time to remove git_blame from gitweb, and git-annotate? Johannes Schindelin
2006-10-06 17:52 ` Luben Tuikov
2006-10-07 5:37 ` Martin Langhoff (CatalystIT)
2006-10-06 16:16 ` Petr Baudis
2006-10-06 18:55 ` Luben Tuikov
2006-10-06 19:08 ` Petr Baudis
2006-10-06 20:21 ` Luben Tuikov
2006-10-09 10:32 ` [PATCH 1/1] Remove git-annotate.perl and create a builtin-alias for git-blame Ryan Anderson
2006-10-09 10:37 ` perhaps time to remove git_blame from gitweb, and git-annotate? Ryan Anderson
2006-10-09 22:33 ` Obituary for git-annotate 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=7vu02jfaec.fsf_-_@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=freku045@student$(echo .)liu.se \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=ltuikov@yahoo$(echo .)com \
--cc=martin@catalyst$(echo .)net.nz \
--cc=martyn@catalyst$(echo .)net.nz \
--cc=pasky@suse$(echo .)cz \
--cc=ryan@michonline$(echo .)com \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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