Re: Statictics on Git.pm usage in git commands (was: [PATCH 2/3] add new Git::Repo API)
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:44:58
Hi, On Sun, 20 Jul 2008, Petr Baudis wrote:
On Sun, Jul 20, 2008 at 02:33:46PM +0200, Johannes Schindelin wrote:quoted
On Sun, 20 Jul 2008, Petr Baudis wrote:quoted
On Sun, Jul 20, 2008 at 12:38:07PM +0200, Johannes Schindelin wrote:quoted
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 don't remember any concrete report of such problems ever reaching me; exactly what trouble are you hitting with the Perl scripts using Git.pm? I will be glad to try to fix it.They reached you: http://article.gmane.org/gmane.comp.version-control.git/23153running Git in-place without correctly setting the prefix is not supported anyway; git wrapper will still be using non-builtin commands from the prefix location instead of your fresh build.
There were none. Anyway, because Git makes it _really_ hard to run in-place, I gave in. I run Git from $HOME/bin now.
It seems I fixed this right away?
That is not what I remember. I remember that I had the next issue right away. I remember that there were problems with ActiveState Perl+Cygwin. And I remember that the Git.xs was not merged in the end. Anyway, this whole discussion is moot, methinks. Let's concentrate back on the real issue: merging the two as-of-now incompatible Perl modules. It really would be nice to have one pony with one saddle in the end, so that the use of Lea's GSoC project is not limited to gitweb with enabled caching. Ciao, Dscho