Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Ok I may have spoken a bit too soon. I did a little research and found out a couple of things. 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. 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. 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? Thanks Matt S. "Matt Schuckmann" <matthew_schuckmann at amat.com> wrote in message news:d2f7ja$7oq$1 at paris.nodomain.org... > Is there a quick and easy way to determine what files have actually changed > on a branch. > > For example, you apply a branch tag to an entire module, do some work, > commit some files to that branch, some time passes and now you want to get a > list of all the files that have actually been commited to that branch? > > Seems like it would be something like a diff between the branch point and > the branch tip but I don't want a full diff I just want a list of changed > file names and paths. > > This seems like a rather common task, is there a simple solution I'm > missing? > > Thanks, > Matt > >