On Sun, Jul 07, 2013 at 06:34:09PM +0200, Stefan Sperling wrote: > By design, there are many cases where the working copy code ends up > searching the directory hierarchy upwards for a wc.db database in > a .svn directory.
Does it stop once it finds one, or does it continue to search further up? I would assume it stops, since it only needs one database. If it stops, then a new checkout would only be 'in trouble', as long as it's own database isn't present yet if I understand this correctly. Then the next question would be when this is created during a checkout: close to the beginning or when the checkout is finished. It probably has to be closer to the beginning, since the checkout code has to work with that new database, and not another that might happen to live in some parent directory. If this is the case, then I would imagine that the critical code during checkout that shouldn't look 'up' might not be that large. Of course, this chain of arguments contained a lot of assumptions and it would take someone more familiar with the code to comment on this. Depending on the results of such an initial assessment someone might be willing to look into it, or maybe not. Frank
signature.asc
Description: Digital signature