1. 19
  1.  

  2. 4

    Putting a unique name in the file itself was how the Arch RCS tracked renames. ISTR it was annoying for some file types, especially if they didn’t have comments—like plain text files, and many data files like CSV, & markdown without extensions.

    1. 4

      Revision-control systems doing things like that (and I see similar things done with CVS and others all over) has always struck me as a severely broken approach at a very fundamental level. An RCS system’s job is to track arbitrary data, not impose requirements on it or modify it in any way. An RCS tool that (as far as I’m concerned) corrupts the data I put in it (or requires me to manually corrupt it myself) is not one I have any use for whatsoever. Thankfully we have sane ones nowadays.

      1. 1

        Yeah, I agree, it wasn’t pretty. Particularly as ISTR the initial recommendation was to use the initial name of the file as the tag (rather than a UUID) so there was a strong desire to rename the tag too if the file was renamed. facepalm

    2. 2

      I suppose this is a pointless complaint, but the analogy of hashing the author’s son’s genome is extremely silly.

      http://en.wikipedia.org/wiki/Epigenetics http://en.wikipedia.org/wiki/Chimera_(genetics) http://en.wikipedia.org/wiki/Developmental_psychology

      (Couldn’t resist adding that last one.)