Fair enough. It sounds like WC redesign is something that's been
investigated before. Is there any documentation or mailing list thread
that lists more of these difficulties or can give me an idea of what
people have thought in the past along these lines? Or was it more of a
general, "Hmm... someone should probably do something about this..."
conclusion.
It's an itch I may be interested in scratching, if I can scratch without
disrupting progress in other areas. I've done a fair amount of library
design (and re-design) in my time. It appears, though, that I should
wait until the core group is ready to apply some brain cells to it to
keep the direction on track and keep the edge-cases in check.
Is anyone with sufficient WC experience interested in discussing and
launching a WC redesign plan soon?
Steve Dwire
-----Original Message-----
From: Greg Hudson [mailto:ghudson@MIT.EDU]
Sent: Thursday, September 02, 2004 12:01 PM
To: Steve Dwire
Cc: dev@subversion.tigris.org
Subject: Re: [RFC] Possible Working Copy refactoring...
[snip]
... We've long acknowledged that the
WC library needs a redesign (although the scope of that redesign isn't
well-understood: do we preserve the on-disk format? Do we preserve the
API? Do we implement the current API as a compatibility layer on top of
the new one?). That redesign would probably need to happen before we
could support multiple WC implementation.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 2 19:26:47 2004