Re: Git and Google Summer of Code 2012

Re: Git and Google Summer of Code 2012

[Jakub Narebski]

On Tue, 20 Mar 2012, André Walker wrote:

> Hello Jakub, I tweeted to you, but as your last tweet was from January, I'm  
> guessing here [personal email via Google Profile] is probably a better
> place to talk.

Actually the discussion of GSoC project application ideas with mentoring
organization[1] should take place in the open, on git mailing list,
git@vger.kernel.org.  (You don't need to be subscribed to send email to
it, and there is custom on this mailing list of Cc-ing all people
participating in discussion; you can read git mailing list via other
interfaces e.g. via GMane.)

Perhaps this should be stated more clearly, for example in application
template[2].

[1]: http://www.google-melange.com/gsoc/events/google/gsoc2012
[2]: https://github.com/peff/git/wiki/SoC-2012-Template

> I'm a Computer Science student from a Brazilian university, and I
> have participated in GSoC last year with The Perl Foundation.
>
> I reworked the Catalyst MVC framework to use an Inversion of Control
> framework called Bread::Board instead of it's home grown component
> loading system. I was supposed to continue my work on it this year,
> we were going to release Catalyst v6.0 with it, but TPF was not   
> accepted in GSoC. I guess we'll have to ship it without GSoC then.
>
> Anyhow, I'd like to participate in it again this year, even if not  
> continuing what I began last year. Preferably using Perl, but I guess I  
> could try something different. And looking in the accepted orgs for GSoC,  
> Git seemed a very cool option, I'd be very honored to work on it. I use git  
> on most of my projects, but I have never delved in it's code.
>
> From the ideas page, I got interested in two items: "Modernizing and
> expanding Git.pm", and "Linus's ultimate content tracking tool".
> To be honest, the latter sounded awesome! But I don't know if I could
> be able to pull it off, as I don't know how complex it would be.

From what I understand "Linus's ultimate content tracking tool" is
rather a sketch of an idea, rather than concrete project proposal.
You would have to carve a project from this proposal yourself.

> I'd be willing to try though, if I could talk to the relevant people,
> understand how the implementation would work, etc.

People on git mailing list could help there, perhaps starting with
person that suggested it.

> And, well, in the first one (Modernizing Git.pm) they pointed   
> you as a possible mentor, so I'd like to know. First, how much of Git is  
> actually in Perl? In other words, how much of it is implemented in Git.pm  
> and related modules, or who would use it exactly? 

There are quite a few git commands implemented in Perl, and there were
even more before "builtin-ification" of git code (moving to C).  Those
include the interactive part of git-add (git-add--interactive helper),
git-cvsimport, git-cvsserver and git-svn, git-send-email, git-difftool
and gitweb.  Not all of those use Git.pm module (git-cvsimport, 
git-cvsserver and gitweb do not); changing this might be part of GSoC
project.

Git.pm currently does mainly cover safe and portable (ActiveState Perl)
invoking of git commands, and a bit of converting / translating
output to Perl (e.g. config_bool() method).

It is by no means complete; some of code could be refactored and moved
from individual commands to Git.pm module.

> Also, why is it not on CPAN? Wouldn't it be useful to other people to
> write interfaces in Perl for Git?

It is not on CPAN probably because Git Development Community lack(s|ed)
a Perl hacker, having only Perl dabblers ;-P

More seriously, putting Git.pm on CPAN might be a part of this GSoC
project.  Not that CPAN lacks git modules: Git::Class, Git::PurePerl,
Git::Repository, Git::Wrapper, Git::XS (libgit2 based)...

Note however that Git.pm must (in my opinion) remain "dual lived" module,
i.e. reside in git.git repository and be installable alongside git
with nothing but git sources.  This also means that any extra non-core
(or even not installed by default with "perl" package) modules that
Git.pm requires to work need to have copy in git.git repository just
like private-Error.pm (should be 'inc/Error.pm') does currently.

Git.pm might ultimately be put in separate repository, and subtree-merged
into git.git like git-gui and gitk subsystems (or as submodule), but that
would require having real maintainer for this module.

> It mentions replacing Error and Error::Simple for Try::Tiny and   
> Exception::Class. What else should be modernized? And where else is there  
> room for expansion?

You could borrow from IPC::Run, Capture::Tiny and similar modules to make
it possible to capture stderr of git commands to separate string or
separate filehandle, or just silencing stderr completely.  Perhaps even
allowing creating pipelines.

You could polish and modernize Git::Object, Git::Commit, Git::Tag,
Git::Repo and Git::RepoRoot from GSoC 2008 project[2], and add similar
modules for other concepts: diff (tree level and patchset level), tree
(directory), refs and refspec, etc.  All those with tests.

[2]: git://repo.or.cz/git/gitweb-caching.git
     http://repo.or.cz/w/git/gitweb-caching.git (gitweb)

You could separate somehow the idea of git commands that do not
require repository like "git version" or "git config --file", or
"git init" (Git::Cmd?), those that require repository but not working
area like "git log" or "git show" (Git::Repo?), and those that require
working area like "git status" or "git pull" (Git::Repo::Workdir?).

You could, for example based on existing gitweb code, create Git::Config
module that would read all configuration at once with `git config -l`,
and not use one git command for one variable like current $git->config()
does.

You could create interfaces to persistent "git cat-file --batch",
"git cat-file --batch-check" and "git diff-tree --stdin".  IIRC gsoc2008
project includes something like that.


And of course borrow^W steal interesting parts of Git::* modules
available on CPAN.

> Do you think we could unite both projects, or it would   
> be too much work? And if you're not the person I should be asking about the  
> content tracking tool, could you point me to that person?

I think it might be too much work, though prototyping "Linus's ultimate
content tracking tool" in Perl might be good idea...

HTH
-- 
Jakub Narebski
Poland

Re: Git and Google Summer of Code 2012

[Junio C Hamano]

Jakub Narebski <jnareb@gmail.com> writes:

> On Tue, 20 Mar 2012, André Walker wrote:
>
>> Hello Jakub, I tweeted to you, but as your last tweet was from January, I'm  
>> guessing here [personal email via Google Profile] is probably a better
>> place to talk.
>
> Actually the discussion of GSoC project application ideas with mentoring
> organization[1] should take place in the open, on git mailing list,
> git@vger.kernel.org.  (You don't need to be subscribed to send email to
> it, and there is custom on this mailing list of Cc-ing all people
> participating in discussion; you can read git mailing list via other
> interfaces e.g. via GMane.)

The parenthesized part applies to general audience but not to GSoC
students, I would think. Isn't the participation in the mentoring
community mandatory for them?

Re: Git and Google Summer of Code 2012

[Jakub Narebski]

On Tue, 20 Mar 2012, Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
> > On Tue, 20 Mar 2012, André Walker wrote:
> >
> > > Hello Jakub, I tweeted to you, but as your last tweet was from January, I'm  
> > > guessing here [personal email via Google Profile] is probably a better
> > > place to talk.
> >
> > Actually the discussion of GSoC project application ideas with mentoring
> > organization[1] should take place in the open, on git mailing list,
> > git@vger.kernel.org.  (You don't need to be subscribed to send email to
> > it, and there is custom on this mailing list of Cc-ing all people
> > participating in discussion; you can read git mailing list via other
> > interfaces e.g. via GMane.)
> 
> The parenthesized part applies to general audience but not to GSoC
> students, I would think. Isn't the participation in the mentoring
> community mandatory for them?

Perhaps being subscribed to git mailing list, and participating in
#git or #git-devel IRC channel (and perhaps also #gsoc channel) is
mandatory for GSoC students (though I think if it is so it should
be stated clearly in materials such as SoC-2012-Template application
template)...

...but is it required also for _prospective_ (would-be) students? 

-- 
Jakub Narebski
Poland

Re: Git and Google Summer of Code 2012

[Jeff King]

On Tue, Mar 20, 2012 at 06:44:54PM +0100, Jakub Narebski wrote:

> > > Actually the discussion of GSoC project application ideas with mentoring
> > > organization[1] should take place in the open, on git mailing list,
> > > git@vger.kernel.org.  (You don't need to be subscribed to send email to
> > > it, and there is custom on this mailing list of Cc-ing all people
> > > participating in discussion; you can read git mailing list via other
> > > interfaces e.g. via GMane.)
> > 
> > The parenthesized part applies to general audience but not to GSoC
> > students, I would think. Isn't the participation in the mentoring
> > community mandatory for them?
> 
> Perhaps being subscribed to git mailing list, and participating in
> #git or #git-devel IRC channel (and perhaps also #gsoc channel) is
> mandatory for GSoC students (though I think if it is so it should
> be stated clearly in materials such as SoC-2012-Template application
> template)...
> 
> ...but is it required also for _prospective_ (would-be) students? 

I would hesitate to ever call anything _mandatory_. A student who is
aware of how the git community works, is up-to-date with recent
discussions on the proposed area of work, and who has interacted with
the developer community will have a much stronger application and be
more likely to succeed in their project.

Given that the mailing list is the center of the development community,
I would expect reading at least some of it to be part of the above
tasks. But whether they want to subscribe, read via nntp, read via list
archives on gmane, or whatever, is up to the student. And I certainly
wouldn't expect them to read every message; instead, they should read
parts that interest them and seem applicable to their proposed work.
Because there is a lot of traffic on the list, it often helps to cull
uninteresting bits by their subject, or whole threads after reading the
first message of a thread and deciding it's boring.

-Peff

Re: Git and Google Summer of Code 2012

[André Walker]

Well, one way or another, I do want to subscribe. I tried to do it 
though, but somehow I'm still not subscribed.

I mailed majordomo@vger.kernel.org with the message body "subscribe 
git". I did it twice, yesterday, and today again. Am I doing something 
wrong, or should I just wait?

On 03/20/2012 02:54 PM, Jeff King wrote:
> On Tue, Mar 20, 2012 at 06:44:54PM +0100, Jakub Narebski wrote:
>
>>>> Actually the discussion of GSoC project application ideas with mentoring
>>>> organization[1] should take place in the open, on git mailing list,
>>>> git@vger.kernel.org.  (You don't need to be subscribed to send email to
>>>> it, and there is custom on this mailing list of Cc-ing all people
>>>> participating in discussion; you can read git mailing list via other
>>>> interfaces e.g. via GMane.)
>>> The parenthesized part applies to general audience but not to GSoC
>>> students, I would think. Isn't the participation in the mentoring
>>> community mandatory for them?
>> Perhaps being subscribed to git mailing list, and participating in
>> #git or #git-devel IRC channel (and perhaps also #gsoc channel) is
>> mandatory for GSoC students (though I think if it is so it should
>> be stated clearly in materials such as SoC-2012-Template application
>> template)...
>>
>> ...but is it required also for _prospective_ (would-be) students?
> I would hesitate to ever call anything _mandatory_. A student who is
> aware of how the git community works, is up-to-date with recent
> discussions on the proposed area of work, and who has interacted with
> the developer community will have a much stronger application and be
> more likely to succeed in their project.
>
> Given that the mailing list is the center of the development community,
> I would expect reading at least some of it to be part of the above
> tasks. But whether they want to subscribe, read via nntp, read via list
> archives on gmane, or whatever, is up to the student. And I certainly
> wouldn't expect them to read every message; instead, they should read
> parts that interest them and seem applicable to their proposed work.
> Because there is a lot of traffic on the list, it often helps to cull
> uninteresting bits by their subject, or whole threads after reading the
> first message of a thread and deciding it's boring.
>
> -Peff
>

Re: Git and Google Summer of Code 2012

[Jeff King]

[-cc everyone but the list, as this will not interest the other people
     directly]

On Tue, Mar 20, 2012 at 03:01:08PM -0300, André Walker wrote:

> Well, one way or another, I do want to subscribe. I tried to do it
> though, but somehow I'm still not subscribed.
> 
> I mailed majordomo@vger.kernel.org with the message body "subscribe
> git". I did it twice, yesterday, and today again. Am I doing
> something wrong, or should I just wait?

It sounds like you are doing it right. And your emails look OK to me
(and the list is accepting them when cc'd). Your original mails may have
been greylisted, and waiting on your mail server to re-send them.
Depending on how your mail server is configured, that might be a few
minutes or a few hours. How long ago did you try?

-Peff

Re: Git and Google Summer of Code 2012

[André Walker]

On 03/20/2012 03:18 PM, Jeff King wrote:
> It sounds like you are doing it right. And your emails look OK to me
> (and the list is accepting them when cc'd). Your original mails may have
> been greylisted, and waiting on your mail server to re-send them.
> Depending on how your mail server is configured, that might be a few
> minutes or a few hours. How long ago did you try?
Right. The first time was more than 11 hours ago, and the second 1 hour 
ago. Is there a list administrator who can whitelist my address?

majordomo subscription woes

[Jeff King]

On Tue, Mar 20, 2012 at 03:26:12PM -0300, André Walker wrote:

> On 03/20/2012 03:18 PM, Jeff King wrote:
> >It sounds like you are doing it right. And your emails look OK to me
> >(and the list is accepting them when cc'd). Your original mails may have
> >been greylisted, and waiting on your mail server to re-send them.
> >Depending on how your mail server is configured, that might be a few
> >minutes or a few hours. How long ago did you try?
>
> Right. The first time was more than 11 hours ago, and the second 1
> hour ago. Is there a list administrator who can whitelist my address?

We can ask postmaster@vger, but before we do that, there's one more
thing to check.  Majordomo will send a confirmation email with a code in
it. Can you check on your end that majordomo's response email wasn't
blocked as spam?

-Peff

Re: majordomo subscription woes

[André Walker]

On 03/20/2012 03:32 PM, Jeff King wrote:
> On Tue, Mar 20, 2012 at 03:26:12PM -0300, André Walker wrote:
>
>> On 03/20/2012 03:18 PM, Jeff King wrote:
>>> It sounds like you are doing it right. And your emails look OK to me
>>> (and the list is accepting them when cc'd). Your original mails may have
>>> been greylisted, and waiting on your mail server to re-send them.
>>> Depending on how your mail server is configured, that might be a few
>>> minutes or a few hours. How long ago did you try?
>> Right. The first time was more than 11 hours ago, and the second 1
>> hour ago. Is there a list administrator who can whitelist my address?
> We can ask postmaster@vger, but before we do that, there's one more
> thing to check.  Majordomo will send a confirmation email with a code in
> it. Can you check on your end that majordomo's response email wasn't
> blocked as spam?
Yes, I re-checked that now to be sure, and there's nothing from 
majordomo there.

Re: majordomo subscription woes

[Jeff King]

Hi vger postmasters,

André is having trouble getting subscribed to git@vger. His majordomo
requests get no response. Can you check on your end if they are being
dropped, or if the responses are somehow not making it out?

Thanks.

-Peff

-- >8 --
On Tue, Mar 20, 2012 at 03:42:41PM -0300, André Walker wrote:

> >>On 03/20/2012 03:18 PM, Jeff King wrote:
> >>>It sounds like you are doing it right. And your emails look OK to me
> >>>(and the list is accepting them when cc'd). Your original mails may have
> >>>been greylisted, and waiting on your mail server to re-send them.
> >>>Depending on how your mail server is configured, that might be a few
> >>>minutes or a few hours. How long ago did you try?
>
> >>Right. The first time was more than 11 hours ago, and the second 1
> >>hour ago. Is there a list administrator who can whitelist my address?
>
> >We can ask postmaster@vger, but before we do that, there's one more
> >thing to check.  Majordomo will send a confirmation email with a code in
> >it. Can you check on your end that majordomo's response email wasn't
> >blocked as spam?
>
> Yes, I re-checked that now to be sure, and there's nothing from
> majordomo there.

Re: majordomo subscription woes

[André Walker]

Attempt #3 failed again =(

Re: Git and Google Summer of Code 2012

[André Walker]

On 03/20/2012 12:37 PM, Jakub Narebski wrote:
> Actually the discussion of GSoC project application ideas with mentoring
> organization[1] should take place in the open, on git mailing list,
> git@vger.kernel.org.  (You don't need to be subscribed to send email to
> it, and there is custom on this mailing list of Cc-ing all people
> participating in discussion; you can read git mailing list via other
> interfaces e.g. via GMane.)
Right, thanks for pointing it out. Either way (doing GSoC or not), it'll 
be cool to join the list.

>  From what I understand "Linus's ultimate content tracking tool" is
> rather a sketch of an idea, rather than concrete project proposal.
> You would have to carve a project from this proposal yourself.
> ...
> People on git mailing list could help there, perhaps starting with
> person that suggested it.
Thanks, I'm still thinking about it. I'll read with more time the e-mail 
in which Linus proposed the idea, and then I'll decide whether to look 
more into it (mail him, etc).

>> And, well, in the first one (Modernizing Git.pm) they pointed
>> you as a possible mentor, so I'd like to know. First, how much of Git is
>> actually in Perl? In other words, how much of it is implemented in Git.pm
>> and related modules, or who would use it exactly?
> There are quite a few git commands implemented in Perl, and there were
> even more before "builtin-ification" of git code (moving to C).  Those
> include the interactive part of git-add (git-add--interactive helper),
> git-cvsimport, git-cvsserver and git-svn, git-send-email, git-difftool
> and gitweb.  Not all of those use Git.pm module (git-cvsimport,
> git-cvsserver and gitweb do not); changing this might be part of GSoC
> project.
>
> Git.pm currently does mainly cover safe and portable (ActiveState Perl)
> invoking of git commands, and a bit of converting / translating
> output to Perl (e.g. config_bool() method).
>
> It is by no means complete; some of code could be refactored and moved
> from individual commands to Git.pm module.
Got it. I'm cloning git's code to help visualize it better.

>> Also, why is it not on CPAN? Wouldn't it be useful to other people to
>> write interfaces in Perl for Git?
> It is not on CPAN probably because Git Development Community lack(s|ed)
> a Perl hacker, having only Perl dabblers ;-P
Haha, I see :) I hope I can be of some help!

> More seriously, putting Git.pm on CPAN might be a part of this GSoC
> project.  Not that CPAN lacks git modules: Git::Class, Git::PurePerl,
> Git::Repository, Git::Wrapper, Git::XS (libgit2 based)...
>
> Note however that Git.pm must (in my opinion) remain "dual lived" module,
> i.e. reside in git.git repository and be installable alongside git
> with nothing but git sources.  This also means that any extra non-core
> (or even not installed by default with "perl" package) modules that
> Git.pm requires to work need to have copy in git.git repository just
> like private-Error.pm (should be 'inc/Error.pm') does currently.
>
> Git.pm might ultimately be put in separate repository, and subtree-merged
> into git.git like git-gui and gitk subsystems (or as submodule), but that
> would require having real maintainer for this module.
Right. Yeah, in a quick look on CPAN I saw those. I understand what you 
mean that it should remain dual lived. Is using local::lib a viable 
option? It would make it much easier to keep everything updated, and 
have new required modules, etc. Though I guess that's something that 
could be decided during development.

>> It mentions replacing Error and Error::Simple for Try::Tiny and
>> Exception::Class. What else should be modernized? And where else is there
>> room for expansion?
> You could borrow from IPC::Run, Capture::Tiny and similar modules to make
> it possible to capture stderr of git commands to separate string or
> separate filehandle, or just silencing stderr completely.  Perhaps even
> allowing creating pipelines.
I don't really understand what you mean by this. I should capture stderr 
for Git.pm, or other git commands? And why would I do that? Is it to 
manually get errors instead of Try::Tiny?

> You could polish and modernize Git::Object, Git::Commit, Git::Tag,
> Git::Repo and Git::RepoRoot from GSoC 2008 project[2], and add similar
> modules for other concepts: diff (tree level and patchset level), tree
> (directory), refs and refspec, etc.  All those with tests.
>
> [2]: git://repo.or.cz/git/gitweb-caching.git
>       http://repo.or.cz/w/git/gitweb-caching.git (gitweb)
Right, thanks, I'm taking a look at that too.

> You could separate somehow the idea of git commands that do not
> require repository like "git version" or "git config --file", or
> "git init" (Git::Cmd?), those that require repository but not working
> area like "git log" or "git show" (Git::Repo?), and those that require
> working area like "git status" or "git pull" (Git::Repo::Workdir?).
>
> You could, for example based on existing gitweb code, create Git::Config
> module that would read all configuration at once with `git config -l`,
> and not use one git command for one variable like current $git->config()
> does.
>
> You could create interfaces to persistent "git cat-file --batch",
> "git cat-file --batch-check" and "git diff-tree --stdin".  IIRC gsoc2008
> project includes something like that.
Sounds reasonable. Though some parts I still have to take a look at the 
code to understand better.

> And of course borrow^W steal interesting parts of Git::* modules
> available on CPAN.
Seems the best way to go :)

> I think it might be too much work, though prototyping "Linus's ultimate
> content tracking tool" in Perl might be good idea...
Yeah, now that you explained better, it's really too much work for GSoC. 
I'd better be realistic and pick one. Probably the Git.pm one is more 
realistic and could be used afterwards by "Linus's ultimate content 
tracking tool", if it's ever made in Perl.

> HTH
It does, thank you very much!

Cheers,
André.

Re: Git and Google Summer of Code 2012

[Jakub Narebski]

On Tue, 30 Mar 2012, André Walker wrote:
> On 03/20/2012 12:37 PM, Jakub Narebski wrote:
> > André Walker wrote:

> > > And, well, in the first one (Modernizing Git.pm) they pointed
> > > you as a possible mentor, so I'd like to know. First, how much of Git is
> > > actually in Perl? In other words, how much of it is implemented in Git.pm
> > > and related modules, or who would use it exactly?
> >
> > There are quite a few git commands implemented in Perl, and there were
> > even more before "builtin-ification" of git code (moving to C).  Those
> > include the interactive part of git-add (git-add--interactive helper),
> > git-cvsimport, git-cvsserver and git-svn, git-send-email, git-difftool
> > and gitweb.  Not all of those use Git.pm module (git-cvsimport,
> > git-cvsserver and gitweb do not); changing this might be part of GSoC
> > project.
> >
> > Git.pm currently does mainly cover safe and portable (ActiveState Perl)
> > invoking of git commands, and a bit of converting / translating
> > output to Perl (e.g. config_bool() method).
> >
> > It is by no means complete; some of code could be refactored and moved
> > from individual commands to Git.pm module.
>
> Got it. I'm cloning git's code to help visualize it better.
[...] 
> > More seriously, putting Git.pm on CPAN might be a part of this GSoC
> > project.  Not that CPAN lacks git modules: Git::Class, Git::PurePerl,
> > Git::Repository, Git::Wrapper, Git::XS (libgit2 based)...
> >
> > Note however that Git.pm must (in my opinion) remain "dual lived" module,
> > i.e. reside in git.git repository and be installable alongside git
> > with nothing but git sources.  This also means that any extra non-core
> > (or even not installed by default with "perl" package) modules that
> > Git.pm requires to work need to have copy in git.git repository just
> > like private-Error.pm (should be 'inc/Error.pm') does currently.
> >
> > Git.pm might ultimately be put in separate repository, and subtree-merged
> > into git.git like git-gui and gitk subsystems (or as submodule), but that
> > would require having real maintainer for this module.
>
> Right. Yeah, in a quick look on CPAN I saw those. I understand what you 
> mean that it should remain dual lived. Is using local::lib a viable 
> option? It would make it much easier to keep everything updated, and 
> have new required modules, etc. Though I guess that's something that 
> could be decided during development.

local::lib is a good solution (which probably didn't exist at the time
of writing Git.pm and putting private-Error.pm in 'perl/' subdirectory.
Whether it is good enough, or should we put required non-core Perl
modules in 'inc/' to be able to install them with Git.pm...
 
Anyway it could be decided at merge time.

> > > It mentions replacing Error and Error::Simple for Try::Tiny and
> > > Exception::Class. What else should be modernized? And where else is there
> > > room for expansion?
> >
> > You could borrow from IPC::Run, Capture::Tiny and similar modules to make
> > it possible to capture stderr of git commands to separate string or
> > separate filehandle, or just silencing stderr completely.  Perhaps even
> > allowing creating pipelines.
>
> I don't really understand what you mean by this. I should capture stderr 
> for Git.pm, or other git commands? And why would I do that? Is it to 
> manually get errors instead of Try::Tiny?

Git commands might print some messages to stderr, even in the case where
result is not considered an error (e.g. "git rev-parse --verify", or
"git cat-file -t").  Gitweb uses string form of 'exec' (well, 'open "-|"'
to be more exact) with " 2>/dev/null" to silence warnings.  I'd like
to be able to silence stderr, or capture it (like command_oneline() etc.
capture stdout) with something like existing command_* commands.
 
[...]
> > I think it might be too much work, though prototyping "Linus's ultimate
> > content tracking tool" in Perl might be good idea...
>
> Yeah, now that you explained better, it's really too much work for GSoC. 
> I'd better be realistic and pick one. Probably the Git.pm one is more 
> realistic and could be used afterwards by "Linus's ultimate content 
> tracking tool", if it's ever made in Perl.

Well, there is a question how many project will be funded by Google...
-- 
Jakub Narebski
Poland