[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Is SVN ready for use?

From: Roman Rytov <rrytov_at_entopia.com>
Date: 2002-12-09 23:01:50 CET

> -----Original Message-----
> From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
> Sent: Monday, December 09, 2002 11:55 PM
> To: Roman Rytov
> Cc: dev@subversion.tigris.org
> Subject: Re: Is SVN ready for use?
>
>
> Roman Rytov wrote:
>
> >What I don't know is how to enforse programmers to update and commit
> >their changes on a regular basis. I asked already about "watch" and
> >because it yet to come I wanna know how people work. Now my team is
> >working with VSS and a version builder detects whether
> someone forgot
> >to check-in files just before building. Unfortunately it
> happens pretty
> >frequently. How to prevent forgetting?
> >
> >
>
> get programmers who don't suck.
>
> seriously, if your programmers can't be taught to type 'svn
> status' to
> see that they have uncommitted modifications in their working
> copy, or
> that they should 'svn update' once a day or more, then you
> should fire
> them and get someone better.
>
> these are basic, fundamental tasks that come with using a version
> control system.
>
> -garrett

That what watch and editors commands stand in CVS for. I didn't mean
that lack of such commands is insurmountable obstacle but it's like
safety measure. If it is it's better.

RR

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 9 23:02:30 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.