WSGI: avoid leaking repository class objects
This is the same as hgitaly!59, except that we can be confident that we aren't serving a repo that was created by `hg share`. Mutualization of some kind would obviously be beneficial, but is prematurate, depending on what we can do upstream (Mercurial or topic extension).
parent
65c0b4d40573
No related branches found
No related tags found
Checking pipeline status
Loading
Please register or sign in to comment