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.

more adventures in CVS 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • While a thoroughly good idea, the time taken to research all varieties of Version Control, is likely to be a long time. How detailed do you go and what apps do you do you cover? Some are limited to specific platforms, others are limited by their accessibity (command line verses GUI). If you do manage it, much respect will be due.

    I was introduced to version control some 15+ years ago, with SCCS and RCS. Scary then and scary still. Thank $deity for CVS :)

    • I did a dissertation on version control as part of my final year project (I also designed and implemented a http-like server that provided abstract info on RCS and ither VCS directories on the server with a GTK client).

      My plan is to cover RCS, which would also give a good introduction to Version Control basics. Then cover CVS and SVN.

      The core of the book would be practical applications of version control

      • the how and why of branching and merging and tagging.
      • perl and shell scripts and recipes for loginfo, reporting, etc
      • Gui's, interfaces, etc
      • Integrating with other applications (mysql, bugzilla, etc)
      • installing and migrating
      • recovering from fuckups
      There will probably be a short bit on 'other' systems like bitkeeper and sourcesafe.

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.