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.
Surely there is a need for it or else people like me and whomever implemented the Move Branch to Head macro in WinCVS wouldn't be doing it. If I remember right if a file changes on the main line but not on a branch when you do a merge from the mainline to the branch a new revision is created on the branch that is identical to the revision on the mainline. In my mind this is wasteful and unnecessary. Plus it makes it difficult to differentiate changes specific to the purpose for the branch and changes related to the mainline. Further more when you merge the branch back to the mainline there are cases where a new revision will be created on the mainline that is identical to the revision before it (I know I've tested this and pointed it out to you). There are people out there using a branch per task (or change set) pattern (I've seem them post on this message board) and it would be nice if the tool nicely supported such a pattern. Matt S. Tony Hoyle wrote: > Matt Schuckmann wrote: > >> Thanks that worked. I kind of knew that was the problem I was just to >> lazy to go figure out how to change the macro. >> >> It would be nice if this was a native command of CVS that way you >> could just tell it to float a whole directory or module and it would >> figure out which files are ok to float the branch on for you. >> > There's no need for it surely - that's what merging does, and it does it > a lot better than mucking around with moving branches... > > Tony