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. The SVN config work around that Kalen mentioned works just fine and I don't see any need to modify tortoise for this feature. On Thursday, July 26, 2018 at 4:08:05 PM UTC-5, Stefan wrote: > > > On Wednesday, July 25, 2018 at 11:19:47 PM UTC+2, Scott Adams wrote: >> >> Is there a way to default to having "keep locks" checkbox checked when >> the commit dialog comes up? >> > > Sorry, no. > Because it's very bad practice to keep a lock on a file for too long. A > lock should only be kept as long as it's really needed, i.e. as long as > you're working on that file and no longer. Having the checkbox checked by > default would lead to a lot of locked files which aren't really worked on > anymore. > > Stefan > -- 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/647907e3-355f-4a05-8201-4561e1b18f3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
