Re: Statictics on Git.pm usage in git commands (was: [PATCH 2/3] add new Git::Repo API)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 20, 2008, 10:38 UTC
- Message-ID
- <alpine.DEB.1.00.0807201233010.3305@eeepc-johanness>
- In-Reply-To
- <200807192254.24622.jnareb@gmail.com>
Hi,
On Sat, 19 Jul 2008, Jakub Narebski wrote:
Show 12 quoted lines
> From git commands in Perl the following include "use Git" in their > sources: git-cvsexportcommit, git-send-email, git-svn, and helper > script git-add--interactive. There are Perl scripts which do not > use Git.pm: git-archimport (which I think should be obsoleted or > moved to contrib), git-cvsimport, git-cvsserver, git-relink. This > means that half of Perl scripts use Git Perl API. > > The situation is worse for scripts in 'contrib/'. From those, only > contrib/examples/git-remote.perl uses Git.pm; neither blameview, > continuous, git-import and import-tars in fast-import, setgitperms > and update-paranoid in hooks, stats, nor other Perl scripts in > examples (git-rerere, git-svnimport) include "use Git".
You call that "worse"? Pasky tried to convert all Perl scripts at once IIRC, and my numerous problems just _making_ the Git scripts led me to rewrite a few Perl scripts in C, so I could safely exclude the Perl scripts from my personal fork.
I guess that it was this experience which prevented more of the old scripts from being converted.
But your mention of git-add--interactive actually brings up my pet-peeve: this script is the only Perl script needed for common operations, i.e. the only reason msysGit has to ship bloated with Perl.
Ciao, Dscho