git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff (CatalystIT)" <martin@catalyst.net.nz>
To: ltuikov@yahoo.com
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org, Petr Baudis <pasky@suse.cz>,
	Jakub Narebski <jnareb@gmail.com>,
	Ryan Anderson <ryan@michonline.com>,
	Martyn Smith <martyn@catalyst.net.nz>,
	Fredrik Kuivinen <freku045@student.liu.se>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: perhaps time to remove git_blame from gitweb, and git-annotate?
Date: Sat, 07 Oct 2006 18:37:26 +1300	[thread overview]
Message-ID: <45273D16.7050205@catalyst.net.nz> (raw)
In-Reply-To: <20061006175234.41182.qmail@web31810.mail.mud.yahoo.com>

Luben Tuikov wrote:
>>>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.
>>
>>+1. Although I would leave git-annotate in git, if only to meet 
>>expectations of new git users.
> 
> 
> I agree with Junio's assessment of the situation.

+1 -- I need to test that the switch to git-blame for git-cvsserver 
works well for Eclipse end users. Will try and fit that next week 
somehow ;-)


martin
-- 
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ  Ltd, PO Box 11-053, Manners St,  Wellington
WEB: http://catalyst.net.nz/           PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224                              MOB: +64(21)364-017
       Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------

  reply	other threads:[~2006-10-07  5:37 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     ` perhaps time to remove git_blame from gitweb, and git-annotate? Junio C Hamano
2006-10-06 13:07       ` Johannes Schindelin
2006-10-06 17:52         ` Luben Tuikov
2006-10-07  5:37           ` Martin Langhoff (CatalystIT) [this message]
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=45273D16.7050205@catalyst.net.nz \
    --to=martin@catalyst.net.nz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=freku045@student.liu.se \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    --cc=ltuikov@yahoo.com \
    --cc=martyn@catalyst.net.nz \
    --cc=pasky@suse.cz \
    --cc=ryan@michonline.com \
    --cc=torvalds@osdl.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).