Ryan Schmidt wrote: > On Feb 13, 2010, at 19:00, Glenn Maynard wrote: > >> A database representing the whole working copy? That's odd--I can't >> think of how that could generally handle actions like cloning a whole >> WC (cp -a wc1 wc2), pulling a piece out of a WC creating a new WC as a >> result (mv wc1/trunk .; rm -rf wc1) and renaming a WC (mv wc1 wc1~), >> all of which work with the current system (and all of which I use with >> varying frequency).
You can't think how that would handle those actions because many of them won't be handled at all. 'cp -a wc1 wc2' will result in a non-working-copy named 'wc2'. 'mv wc1/trunk .; rm -rf wc1' will result in a non-working-copy named 'trunk'. And so on. There's been talk of adding 'svn' tool support for these actions, of course, but I don't know if the details have been decided upon. Why don't you chime in over on dev@, since that's rather the place to discuss Subversion's development? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
