Of course, if they're Windows users all bets are off... :-/
On Jan 16, 2008 10:49 AM, Peter Connolly <psconnolly_at_gmail.com> wrote:
> Thomas, Karl, et. al.,
>
> I just wanted you to know that I am a big Subversion fan, having
> switched from CVS a couple of years ago. That said, "Herman - Temp"
> sounds like a version control newbie (No offense, please! Everyone has
> to start somewhere.) with a use case that basically wants/needs a
> single-threaded development model that avoids merging. Given that
> merging is one of the big boogeymen for newbies, RCS would provide a
> simple introduction to version control that automatically "locks"
> checked-out files and that avoids all the overhead of installing and
> configuring either CVS or Subversion.
>
> pc
>
>
> On Jan 16, 2008 1:53 AM, Thomas Hemmer <themmer_at_go-engineering.de> wrote:
> > Peter, Herman,
> >
> > there is no reason at all to avoid subversion ;-)
> >
> > Although SVN does not provide any means to *automagically* lock a file
> > on check out it still supports a locking mechanism.
> > In fact this does not impose any restriction: after having checked out
> > some file, anyone is free to make their changes to it without doing any
> > harm to you.
> > The only rule to be obeyed is that whoever is going to edit the file
> > *must* set a lock before (For safety, you might perform an "svn update"
> > prior to locking). The one who "wins the race" does his/her changes and
> > commits them when done.
> >
> > As soon as the lock owner has released it it's your turn.
> >
> >
> > Happy versioning,
> >
> > Thomas
> >
> >
> > > -----Original Message-----
> > > From: Peter Connolly [mailto:psconnolly_at_gmail.com]
> > > Sent: Wednesday, January 16, 2008 5:37 AM
> > > To: Herman - Temp
> > > Cc: users_at_subversion.tigris.org
> > > Subject: Re: Question about Subversion features
> > >
> >
> > > If you want each developer to have exclusive use of a file
> > > that they are changing and you want to avoid merging, then
> > > you should probably be looking at RCS and avoiding Subversion and CVS.
> > >
> > > On Jan 15, 2008 6:54 PM, Herman - Temp
> > > <Herman_at_synergixtech.com> wrote:
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm currently doing evaluation on versioning control system.
> > > > Subversion is one of my consideration to be used in the
> > > company where
> > > > i'm employed. There are around 10 developers in this company.
> > > > Occasionally, when a file need to be merged, the old code is
> > > > overwritten by the new code. So, I want to know whether
> > > Subversion has
> > > > the feature to automatic lock a files that is already
> > > checkout-ed for
> > > > editting? Or Is there any suggestion to reduce the code merging to
> > > > happen? How does Subversion handle binary file? (Note:
> > > Binary file cannot be merge normally, right?).
> > > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > > Herman.
> > > >
> > >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> > > For additional commands, e-mail: users-help_at_subversion.tigris.org
> > >
> > >
> >
> >
> >
> > GO Engineering GmbH - Stolzenbergstr. 13/IV - 76532 Baden-Baden
> > Geschäftsführer:
> > Helmut Gerstner, Dipl.-Ing. (FH)
> > Ralf Wörner, Dipl.-Ing. (FH)
> > Registergericht: Mannheim HRB 201811
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> > For additional commands, e-mail: users-help_at_subversion.tigris.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-16 20:03:13 CET