8/15    Is there a cvs equivalent to the clearcase predecessor diff?
        I can do a cvs status, subtract 1 from the minor version and
        then do a cvs diff -r<version> but I'm looking for something
        built-in.
        \_ How exactly is that not built in?
        \_ If you want to diff your _working_ version to the latest checked
           in version, you can just say "cvs diff filename" (no revisions)
           Don't know if that helps...  --dbushong
           \_ I'm looking for something that tells me the difference
              between the latest version in cvs and its immediate
              predecessor. If someone else works on my code and commits
              say 1.3, while my last version was 1.2, I want to see the
              difference between these two versions. In clearcase you
              can just say ct diff -pred <file>.
              \_ Wouldn't it make MORE sense to branch this code so
                 that YOU knew what the prior version was?  --sowings
                 \_ In my situation branching isn't appropriate. I'm
                    sometimes stuck in a position where the latest rev
                    of a file breaks a particular feature, so I want
                    to know what all changed between the two revs so
                    its quicker for me to figure out where the problem
                    is and fix it. Its not a big deal, I went ahead
                    and wrote a little perl script that does my diffs
                    for me.
                    \_ This is why you set a commit policy. cvs doesn't
                       negate the need for communication.
                       \_ Can you set a commit policy on a particular
                    \_ No, [32mreallï[0m  --dbushong
                    \_ No, [32mreallM-o[0m  --dbushong
                          file/dir? I though it was per module only.
        \_ what we do is create a cvs wrapper program that adds extra
           features like that, and file locking. ours is just a perl script.
           \_ I asked around at work and it looks like I'm going to have
              do the same. I guess I'm just too used to a professional
              revision control system.
              \_ I mean that's definitely useful, but it's not under the
                 heading of a killer integral feature..  If you can easily
                 hack something that does it for you with a perl script
                 in 2 minutes, it's not overly important.  I tend to do my
                 diffs with cvsweb anyway; the colored thingy makes it much
                 easier to see at a glance what changed (and I'm not the type
                 that usually likes pretty colored things)  --dbushong
                 \_ Sure you aren't...
                    \_ No, [1;32mreally[0m  --dbushong
                 \_ I personally like the graphical version browser in cc.
                    Its much easier to use than that crufty cvsweb thing.
                    Its all the little things that I have to tack on to
                    cvs to make it more professional a la cc that annoy me.
               \_ there's always xdiff, if you can dig it up.
                  \_ I normally use diff -s (side by side, which doesn't
                     require X11 running)
                     \_ However, it requires GNU diff. And the flag conflicts
                        with standard diff.
                        \_ Doesn't solaris ship with sdiff (same as diff -s)?