On Tue, Nov 27, 2007 at 05:40:40PM +0100, Fabien Meghazi wrote:
> > It is not possible to do this today. It would be a major rewrite of
> > the client libraries to do this.
> I didn't realized it would required so much work. I was thinking about
> a patch that would simply change behaviour of svn command like this :
> Pseudo Code
> 6. if .svn folder is "marked" as "single .svn mode"
> 7. # we are in the root of a "single .svn" repository
> 8. set some variable state for further patching
> 9. else
> 10. # we are in a standard (not single .svn) repository
> 11. set some variable state for further patching
> 12. end if
What are you trying to gain by creating two different ways of how
the admin area is handled?
In your proposal, the top-level .svn directory mirrors the working
copy anyway, so your goal cannot be to improve performance.
Performance would even be worse in some cases, because if you move
a directory you'd have to keep the tree in your global .svn directory
in sync with the working copy state.
I recommend you read the subversion/libsvn_wc/README file if you
have not read it already. It explains a lot of the reasons behind
the current design. Some shortcomings of the current design are
documented in notes/wc-improvements.
AFAIK the idea of a global .svn directory has been coined before,
but more in a context of a general working copy redesign/rewrite,
instead of adding additional complexity to an already complex
library -- libsvn_wc is, at least according to Karl Fogel and Michael
Pilato who told me this in person, one of the most complex areas
in the subversion code that few developers want to mess with.
Stefan Sperling <email@example.com> Software Developer
elego Software Solutions GmbH HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12 Tel: +49 30 23 45 86 96
13355 Berlin Fax: +49 30 23 45 86 95
http://www.elego.de Geschaeftsfuehrer: Olaf Wagner
Received on Tue Nov 27 18:00:58 2007
- application/pgp-signature attachment: stored