I guessed as much ... the classic email discussion/edit, with all the
attendant problems. :(
I don't really think this is solvable by Subversion or any other scc
system unless everyone has access to it. In a pure serial workflow
the problem is trivial; the current version is owned by whoever has
it. Of course this never works ... its serialized so too slow,
someone gets the document and then goes on vacation leaving it in
their inbox etc etc. That's really what the various WebDAVish
document repository systems try to solve (though not very well, imho).
fwiw, if you aren't going to roll out svn for everyone, then frankly
its not going to help with the issue regardless of rev# issues.
--Tim
On Nov 14, 2006, at 2:06 PM, Les Mikesell wrote:
> On Tue, 2006-11-14 at 13:33 -0800, Tim Hill wrote:
>> I guess it would help to understand the workflow better. You
>> mentioned talking over the phone and people who the document but do
>> not have access to svn or the repository. What is the intended usage
>> here? There is probably some form of tagging that will give you what
>> you want.
>
> I was thinking of the type of document that might be passed around
> and reviewed by a committee of people who don't have direct access
> to the repository and may or may not do any actual revisions to the
> text (returning it to someone to commit) but always need to know if
> the copy they are viewing is current.
>
> --
> Les Mikesell
> lesmikesell@gmail.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 00:23:33 2006