git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git.pm

From
Subho Banerjee <subs.zero@gmail.com>
Date
Apr 26, 2012, 20:10 UTC
Message-ID
<CAB3zAY0NeXuH-wXyYkbim5U74eANY4hq5D6SsVLu3KeUqHFqzQ@mail.gmail.com>
In-Reply-To
<CAFouetgwRpB1GFJOC8PTVryVY-94S3xa5ZiSaWQWoz070qQ-6g@mail.gmail.com>

Hello, I will take care that I dont break those. Should the tests in the t/ folder of the codebase be enough to make sure everything is working as it should be even in the Git perl module? Also is there anything like a public build server which actually catalogs which tests are currently failing so that I know what has gone wrong after my changes, or are all commits supposed to pass every test?

Cheers, Subho.

On Fri, Apr 27, 2012 at 12:28 AM, Tim Henigan <tim.henigan@gmail.com> wrote:
Show 20 quoted lines
> 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.perl
>
> There 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.
Previous: Tim HeniganNext: Jonathan Nieder
Message 4 of 24 in “Git.pm”
  1. Subho BanerjeeApr 26, 2012
  2. Randal L. SchwartzApr 26, 2012
  3. Tim HeniganApr 26, 2012
  4. Subho BanerjeeApr 26, 2012
  5. Jonathan NiederApr 26, 2012
  6. Subho BanerjeeMay 10, 2012
  7. Jonathan NiederMay 10, 2012
  8. demerphqMay 10, 2012
  9. Subho BanerjeeMay 10, 2012
  10. demerphqMay 10, 2012
  11. Junio C HamanoMay 10, 2012
  12. demerphqMay 10, 2012
  13. Andrew SayersMay 10, 2012
  14. demerphqMay 11, 2012
  15. Randal L. SchwartzMay 11, 2012
  16. Junio C HamanoMay 11, 2012
  17. [GIT.PM 1/3] Ignore files produced from exuberant-ctagsSubho Sankar Banerjee, May 19, 2012
  18. [GIT.PM 2/3] Getting rid of throwing Error::Simple objects in favour of simple Perl scalars which can be caught in eval{} blocksSubho Sankar Banerjee, May 19, 2012
  19. Andrew SayersMay 19, 2012
  20. Subho BanerjeeMay 23, 2012
  21. Andrew SayersMay 23, 2012
  22. [GIT.PM 3/3] Perl code uses eval{}/die instead of Error::Simple and Git::Error::CommandSubho Sankar Banerjee, May 19, 2012
  23. Junio C HamanoApr 26, 2012
  24. Sam VilainApr 26, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.