> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Thursday, 4 August 2005 10:55 PM
> Perhaps you can create a special branch for the secretary,
> and let her mount that branch. Then, using autoversioning,
> she can make any changes she wants via drag-n-drop. When
> she's done working, someone who knows Subversion can run 'svn
> merge' to port her branch changes to the trunk (or 'current',
> or whatever you call it.)
We have looked at that option but it has its flaws. Firstly, it's relying
on drag & drop to make cheap copies - the temptation for copy/paste would be
too great. Secondly, once it's up and running, none of the tech staff will
want to touch it beyond backing up the repository, the odd ACL's and
upgrades. We're thinking beyond the division level here and more at the
organisational level.
I think the patch would be easy to make, and if I looked I could probably
even make it myself. However, such a patch probably wouldn't be approved at
work if it wasn't a supported patch.
There are plenty of workarounds, but none is as transparent a solution for
the users as an overwrite copy. In running my test script the solution is
perfect except for the extra delete step (or the move step if you like).
We could easily script working copies in much the same way, but how often do
you think non tech staff will be committing and updating working copies?
I've yet to see a technical argument against copy overwrite, but if there is
one it would at least give some logic as to why *not* to make such a change
to subversion. WebDAV with autocommit already seems to be a first step to
non-tech-user operation of subversion, so why not take it a step further?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 4 21:54:00 2005