Hello Jakub, I had some time to look through the perl module in the Git sources and I wanted to summarize the changes that need to be made - [Primary Task] [1] Move exception handling from Error::Simple to Try::Tiny and Exception::Class [Additional] [2] A Git::Config module that parses the .gitconfig file and the .git/config file in each repository(Is it one of these files or both?) [3] Parsing Tree and Commit objects and then traverse the tree structure in Perl through a Git::Commit module. [4] Cleaning-up improving the API. In general move towards an module that can access and change data in the configuration and commit status using Perl instead of the fork and IPC being used now. Is this what you expect as a part of the GSoC work? Could you please tell me if I am missing something. Cheers, Subho. On Sun, Mar 18, 2012 at 10:01 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > > Subho Banerjee <subs.zero@xxxxxxxxx> writes: > > [...] > > I had a look at the "Ideas" page on the GSoC website and I really > > liked two particular project ideas, in which I believe I can > > contribute to a larger extent. > > > > * Improving parallelism in various commands > > * Modernizing and expanding Git.pm > > [...] > > From what I understand of these tasks -- > [...] > > * For the second one, which aims at improving the Git perl module. I > > tried looking around for this one on the net. I was a little confused > > since I could not make out which module this was on CPAN. Is this one > > of the Git::* modules or is it all of them. Because the the > > functionality of the Git::Config and Git::Commit as mentioned in the > > Ideas page seems to be there in the Git::Repository module on CPAN. > > Could some one please clarify this. > > The "Modernizing and expanding Git.pm" project refers to the Git > module in git sources[1], that is used by git commands implemented in > Perl like git-svn, git-send-email, and interactive part of git-add. > > It is not on CPAN (though if you feel like it putting it on CPAN might > be part of this project, but it must be "dual-lived"). > > [1]: http://repo.or.cz/w/git.git/blob/HEAD:/perl/Git.pm > http://git.kernel.org/?p=git/git.git;a=blob;hb=HEAD;f=perl/Git.pm > https://github.com/git/git/blob/master/perl/Git.pm > > You can of course take inspiration and code (if it is with compatibile > license) from various Git::* modules on CPAN to implement the > "expanding" part of this project. > > Note that Git.pm must remain extremly portable, which includes > ActivePerl on MS Windows (msysGit or Cygwin). Use of non-core modules > (for 5.8.0) should be also probably limited. > > > I would really appreciate any ideas or advice for making my > > application for GSoC 2012 better. > > HTH > -- > Jakub Narebski > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html