# [cvsnt] Re: Determine What files have changed on a branch

Charles L. Farbstein charlie.farbstein at titan.com
Thu Mar 31 00:49:27 BST 2005

```On Wed, 2005-03-30 at 15:19, Oliver Giesen wrote:
> Matt Schuckmann wrote:
>
> > 1. There is a --brief option for the diff command that gives a small
> > amount of information on the differing files, i.e. Repository file
> > name, revisions and some useless text about some temporary files.
>
> Yes, the mentioning of temp files has definitely degraded the
> usefulness of the command. It wasn't always this way.
>
>
> > It doesn't appear that this option is in the documentation but I
> > could have missed it, it's definatly not documented in the online
> > help.  Also it appears that this option doesn't work for the rdiff
> > command which is too bad, perhaps this is a known bug.
>

In the cvshome cvs: "cvs -H diff" documents the --brief option.  For
"cvs rdiff" the -s gives a one-liner for each file. See cvs -H rdiff".

> I'm pretty sure this used to work at some point.
>
>
>
> > 2. Apparently in the past CVS users have been advised to apply a both
> > a branch point tag and a branch tag whenever a branch is made, just to
> > facilitate this type of operation.
> > Is this still the case?
> > If so that's disappointing considering all the wonderful work that
> > has been done with mergepoints it seems that identifying the branch
> > point would be extreamly simple.
> >
> > Is there a reason why CVSNT can't identify the branch point for you?
>
> While we're at it, here's my feature suggestion:
> Introduce some kind of shorthand notation for referring to
> branchpoints, something like
>
> cvs up -r\branch
>
> i.e. use a backslash or whatever other character seems sensible here as
> prefix to the branch name.
>
> Cheers,
--
Charles L. Farbstein
Titan Corp.
Tactical Services Division