Re: Newby : moving/renaming files loses version information?

[Greg A. Woods]

[ On , May 16, 2001 at 18:18:45 (-0400), Laine Stump wrote: ]
> Subject: Re: Newby : moving/renaming files loses version information?
>
> It makes it more difficult to do a diff of a revision of the file
> pre-move with one that is post-move, especially with a frontend such
> as tkCVS, which presents you with a graphical representation of the
> file history, then allows you to click on the two revisions you want
> to diff.

No different or more difficult than diffing any two files!  :-)

pedantically:

        cvs update -p -r old.rev oldname > oldname-old.rev
        cvs update -p -r new.rev newname > newname-new.rev
        diff oldname-old.rev newname-new.rev | more

efficiently, if you want to compare with the current rev of the new file:

        cvs update -p -r old.rev oldname | diff - newname | more

I've occasionally thought of writing a wee function in PCL-CVS to get a
specified revision of a specified file into a buffer so that I can use
ediff, but I do it so rarely it's just not worth the effort.

One thing PCL-CVS doesn't have (which CVSweb does, for example) is a
quick and dirty way of "seeing" the files in the Attic and thus being
able to operate directly on them.  This would help PCL-CVS users not
only with removed files, but with files existing only on branches that
the current working directory is not viewing.  If "cvs status" had an
option to show "Attic" files (actually any file from the repo that's not
in the current working directory's view) then adding such a feature to
PCL-CVS would be quite easy....  It could use "cvs ls", but that's
rather hackish IMHO.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>