On Fri, Jan 10, 2020 at 12:36 AM Nathan Hartman <[email protected]> wrote: > Okay so this is what I suggest: > > Closing this issue (4588), and creating a new issue with a proper title and > description of the root problem, referring to 4588 as an example of how the > problem manifests, and to the archived mailing list discussions.
Ping... I think SVN-4588 should be closed. The original problem resolved itself. (Any objections?) My question is, should we: (A) Create a new issue that describes the root cause; it would refer to SVN-4588 and mailing list discussions for context. or (B) Not file a new issue; close SVN-4588 and declare that this is not a problem as changing a repository while the server processes are running is an unsupported use case. Thanks, Nathan
