Changes between Version 8 and Version 9 of Notes/SubversionAndRCS


Ignore:
Timestamp:
02/08/08 13:55:59 (16 years ago)
Author:
VincentMcIntyre
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Notes/SubversionAndRCS

    v8 v9  
    13135) Lack of per-file versioning will make it inconvenient to perform   the common task of determining at what revision a particular change   to a source file was made.  Currently I do a binary chop on the RCS   version number for the file, but with svn, changes to a file are   tagged with non-consecutive global version numbers.
    1414
    15 6) Presumably because of global versioning, 'svn log' provides no   indication of the extent of changes made to a file at each
    16    revision.  'rlog' does and it's a handy feature that I often use.
     156) Presumably because of global versioning, 'svn log' provides no   indication of the extent of changes made to a file at each   revision.  'rlog' does and it's a handy feature that I often use.
    1716
    18 7) In svn, $Id$ tags must be enabled explicitly for each individual   file that needs it.  Bizarrely, svn allows this to be set up
    19    automatically via auto-props in config files on a per-user or   per-host basis, but not for the repository itself.  This means
    20    that manual intervention is required on a per-file, per-user, or   per-host basis.
     177) In svn, $Id$ tags must be enabled explicitly for each individual   file that needs it.  Bizarrely, svn allows this to be set up   automatically via auto-props in config files on a per-user or   per-host basis, but not for the repository itself.  This means   that manual intervention is required on a per-file, per-user, or   per-host basis.
    2118
    22198) The $Id$ tags are not replaced in source files visible on the web   site e.g. http://svn.atnf.csiro.au/miriad/trunk/prog/clean.for