Re: Git.pm
- From
Tim Henigan <tim.henigan@gmail.com>
- Date
- Apr 26, 2012, 18:58 UTC
- Message-ID
- <CAFouetgwRpB1GFJOC8PTVryVY-94S3xa5ZiSaWQWoz070qQ-6g@mail.gmail.com>
- In-Reply-To
- <CAB3zAY3-Bn86bCr7Rxqi4vxbYFxUesLwm8gddxyMSexov2tOhw@mail.gmail.com>
On Thu, Apr 26, 2012 at 12:15 AM, Subho Banerjee <subs.zero@gmail.com> wrote:
> > ---> I see in the code that it says that the API is experimental. Is > there any absolute need for backward compatibility, or can I try to > redesign the API somewhat extensively?
A quick grep of the code in 'master' shows Git.pm used in the following:
- contrib/examples/git-remote.perl
- git-add--interactive.perl
- git-cvsexportcommit.perl
- git-send-email.perl
- git-svn.perl
- t/perf/aggregate.perlThere is also work in progress on 'pu' that relies on Git.pm.
Breaking any of these scripts would be bad. You may be able to refactor them at the same time Git.pm is modified, but it would be wise to contact the authors before making any major changes.