From: Andreas Ericsson <ae@op5.se>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file.
Date: Thu, 09 Feb 2006 13:47:00 +0100 [thread overview]
Message-ID: <43EB39C4.3020309@op5.se> (raw)
In-Reply-To: <cda58cb80602090404o4e753839g@mail.gmail.com>
Franck Bui-Huu wrote:
> 2006/2/9, Junio C Hamano <junkio@cox.net>:
>
>>Andreas Ericsson <ae@op5.se> writes:
>>
>>
>>>So long as we never involve ruby, java or DCL, I'm a happy fellow.
>>
>>Wholeheartedly seconded ;-).
>>
>
>
> I agree to but my point was more why not only using python scripts ?
> Why sometimes some scripts is written in perl whereas python could be
> used and vice-versa ?
>
Perl is better suited for some tasks, Python for others. Mostly it's
because the contributor (one out of 137 to date) thought the language
appropriate for the tool he/she set out to write and felt comfortable
with it.
I personally abhor the syntax of Perl and the block indentation of
Python but I happily embrace both if the alternative is to rewrite all
the script tools in C.
That said, some tools have been rewritten in the past (mostly scripts
have been replaced by C code versions), but I don't think Junio will
accept replacement tools just because they're in one particular
language. If anything, it would be to replace the two python scripts
with Perl versions, since more tools are implemented in Perl than in
Python (so we could drop one dependency), Perl exists on more platforms
(so git becomes more portable), and Perl is used inline in four of the
shell-scripts (which means we can't get rid of the Perl dependency
without major hackery anyway).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-02-09 12:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 14:52 [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file Ryan Anderson
2006-02-08 15:09 ` Peter Eriksen
2006-02-08 16:05 ` Johannes Schindelin
2006-02-08 16:35 ` Franck Bui-Huu
2006-02-08 17:45 ` Johannes Schindelin
2006-02-08 19:19 ` Junio C Hamano
2006-02-10 11:25 ` Ralf Baechle
2006-02-10 11:55 ` Andreas Ericsson
2006-02-14 10:51 ` Fredrik Kuivinen
2006-02-08 18:47 ` Randal L. Schwartz
2006-02-09 9:19 ` Andreas Ericsson
2006-02-09 9:57 ` Junio C Hamano
2006-02-09 12:04 ` Franck Bui-Huu
2006-02-09 12:47 ` Andreas Ericsson [this message]
2006-02-08 19:09 ` Linus Torvalds
2006-02-08 19:51 ` Junio C Hamano
2006-02-08 21:07 ` Ryan Anderson
2006-02-08 21:45 ` Junio C Hamano
2006-02-10 22:04 ` Ryan Anderson
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=43EB39C4.3020309@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=vagabon.xyz@gmail.com \
/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).