Travis P wrote:
> Re: serializing
>
> When I'm committing and want to look at a diff, it's nice to be able
> to 'svn diff' in another terminal. I'd guess I'm not the only one
> that likes to do this. I assuming Serializing would not allow this.
> Also, some people might be doing this under-the-covers, for example,
> using a script like Julian's (
> http://svn.haxx.se/dev/archive-2004-10/0577.shtml ) and unlike him,
> using status and/or diff used to generate a default log message within
> the commit process as part of their editor invocation (rather than
> prior to commit is as Julian mentions is his habit).
But I said before that if we allow non-modifying operations such as diff
during a modifying operation such as update or commit, then the whole
thing is broken anyway. We can't allow multiple readers /and/ a single
writer to access the WC, only multiple readers /or/ a single writer.
What I'm saying is that the multiple-reader idea isn't really useful anyway.
> As an alternative: maybe an operation can reserve the right to repair
> timestamps and other processes would then proceed without bothering if
> that reservation were not available?
Ah, so you'd solve the problem by adding another lock to the WC.//
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 24 22:46:11 2004