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.
> 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... True, but the exceptions exist. E.g. our case with shared binary files, which are changing in their HEADs but are used over several developer branches in several different, and otherwise independent, modules. Thanks all for pointing me where to look. Should the magic branches work in 2.0.58d ? Best Regards, JP > -----Original Message----- > From: cvsnt-bounces at cvsnt.org > [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Tony Hoyle > Sent: Monday, October 17, 2005 20:47 > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: [cvsnt] Re: virtual branches ? > > 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 > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs > > _____________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > _____________________________________________________________________ This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited. If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution. Thank you.