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

Oliver Giesen ogware at gmx.net
Thu Mar 31 00:19:39 BST 2005


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.


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.

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,

-- 
Oliver
----  ------------------
JID:  ogiesen at jabber.org
ICQ:  18777742     (http://wwp.icq.com/18777742)



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook