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.
Kevin wrote: > This syntax is very useful as you cannot specify a module in update. If > there were new folders added (to trunk, for example) I need to specify -d to > make sure the folders are created on the branch too. However update gets > *all* folders irrespective of the module that I have checked out. How I can > do an update + merge filtering the files by module (and getting any new > folders created for the module only)? modules2 already solves all these problems (at least it will when there's a stable release of the final version) and is able to do it all server-side, so you don't have to update clients - a major disadvantage of trying to fudge the existing modules system to handle this. I intend to transition to using this as fast as possible... since it does seem this checkout 'workaround' is used by more than a few people. Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle <tmh at nodomain.org> Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917