Actually I didn't practice SVN in the company but there are some of
not-technical people here and I wouldn't like to let them even care
about merge. They experience problems on much simplier level.
What my group (as R&D people) needs is to somehow to recall to take the
latest version from a repository. CVS or VSS both have "watch"-like
functionality and closely integratable with almost all IDEs (that I'm
sure SVN also can). So in these cases it's up to an IDE to remind to a
developer to chek-out/in a file (actually it obliges her).
I have to confess that I rather ask how to organize work then argue
about it. I believe SVN in the current stage is workable also but I
wanna underatand the whole workflow.
RR
> -----Original Message-----
> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> Sent: Monday, December 09, 2002 5:37 PM
> To: Roman Rytov
> Cc: dev@subversion.tigris.org
> Subject: Re: Is SVN ready for use?
>
>
> "Roman Rytov" <rrytov@entopia.com> writes:
> > really important since exclusive lock doesn't exist but
> inside a team
> > I can't rely on carefull manual merging (I mean I don't
> want to oblige
> > people to ever think about it).
>
> What happened when you tried the non-locking model?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 9 17:52:09 2002