Hi! We have used a precommit hook for that that controls write access on a by-username-by-folder base.
Mit freundlichen Grüßen Dr. Hartmut Niemann Siemens AG Mobility Division Rolling Stock Standardization, Remote Control, Display MO RS LM EN CCI SRD Werner-von-Siemens-Str. 67 91052 Erlangen, Deutschland Mobil: +49 173 5342327 mailto:[email protected] www.siemens.com/ingenuityforlife<https://siemens.com/ingenuityforlife> [www.siemens.com/ingenuityforlife] Von: Scott Adams via TortoiseSVN [mailto:tortoisesvn+apn2wqcmz_iemerxs1cdc6afxpnk8aym_chhncizbu3r8_pvz...@googlegroups.com] Gesendet: Donnerstag, 26. Juli 2018 23:26 An: TortoiseSVN Betreff: Re: Can I have "keep locks" the default at commit? Yes in general I agree with that Stefan. We have some special case files that are owned by only one master developer. They are not in a standard computer language but one that we use a specially configured Beyond Compare to find our diffs with. Others can make changes but they do it in their own branches. The master developer then merges those changes and commits them in the trunk. The reason we are putting locks on them now is we have been used to everyone touching the trunk. This helps remind them to stay in their branches. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1AE3002F400CE4498072DFDF74A843CC20FA8CAD%40DEFTHW99EH3MSX.ww902.siemens.net. For more options, visit https://groups.google.com/d/optout.
