Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Mastering Perl sources now in Git 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Why did you choose git?

    • I'm not into the religious stuff and I'm content for people to use whatever works for them.

      First, Randal forced me to use git. He got into it very early, and at Stonehenge we use it for anything new. For the Mastering Perl stuff, Allison previously hosted a subversion repo for me on her personal box since she was the book editor, but she moved all of her stuff to a hosted solution. I had the repo sitting on my local box and wanted to make it public, so I changed it to git which I was already using.

      Second, I

      • I've been moving my stuff to github as well. It has a nice interface without a lot of hassle.

        I wish it had some sort of issue tracker, though.
        Google Code *does*, and apparently, you can tell Google Code to advertise github as your repository.
        I may have to take advantage of that feature in the future, unless I find a better issue tracker.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.