> > Also is there a work-a-round?
>
> You can always use properties, and a pre-commit step that rejects
> commits to files which have "locked" property set.
It's more complicated than that because I want to prevent people from
modifying binary files which are "locked". At commit time it's too late,
someone may have done an hour of changes on the file. I understand the
developers of SVN are against file locking, but when a lot of users are
requesting it, and even refusing to use SVN until it has locking, I really
think it should be a higher priority.
> Agreed, but are you REALLY prepared to get all the problems of CVS, in
> exchange for _one_ feature which:
>
> - is easily fixed by people talking to eachother/coordination
> - isn't really guaranteed to work in CVS
I hate CVS. But I don't see many options. Also complicating the fact is
that there is not yet a SVN integration with WebSphere Studio (WSAD) but
that's just a question of time.
> Note, that for binary files in CVS:
>
> - commit time is linear in the size of ALL previous versions of the
> file. Trust me, this is going to be a problem with just a few edits of
> word-files.
> - tagging is linear in the size of ALL the versions that EVER existed
> of all the files tagged
I've used CVS with word files and haven't seen this but it was on a small
project. And the file locking did work, using WinCVS.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 21 13:48:33 2004