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 :)

    • Re:Brave Man (Score:1)

      by dws (341) on 2003.04.07 11:48 (#18838) Homepage Journal
      While a thoroughly good idea, the time taken to research all varieties of Version Control, is likely to be a long time.

      Berczuk and Appleton do a high-level skim of the common version control packages in Software Configuration Management Patterns [amazon.com], though they focus on laying out a common language for talking about SCM, and on high-level patterns of usage, and don't get down to the level of actually giving concrete example of how to use product X. Still, if you're going to write a book on CVS, it might help to look over a larger conceptual framework first, at least to avoid the myopia that comes from only ever having used one or two tools.

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