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.
Gerhard Fiedler wrote: > All situations where the feature is helpful, and it being client-side is > appropriate. (In all cases it is a decision of the sandbox owner, not the > repository admin, what to get and what not.) Sounds reasonable. It's more dynamic than I thought from your initial description as well -- changing it after the initial checkout just for awhile, then removing it. Sort of 'freezing' portions of your sandbox without updating to a sticky tag. Thanks for the insights. Anyone else have an opinion on this vs. other ideas on updates and sandbox management? If there was a way to combine this type of 'freeze' with something to ignore bin directories until a release, that could be helpful. A 'freeze' status with an override on ci, tag or a freeze enable|disable that helps manage the 'sometimes' committed files. Thoughts? Regards, -- Glen Starrett