Re: AW: Multiple cvs users in one checkout area

[Greg A. Woods]

[ On Monday, October 21, 2002 at 09:05:49 (+0200), Andreas Otte wrote: ]
> Subject: AW: Multiple cvs users in one checkout area
>
> The sources are sources for database objects (stored procedures,
> triggers, ...) which are applied against a database, no user has it's
> own database, so it makes no sense to work in different areas,
> everbody will see everybody else's changes in the database anyway. The
> private sandbox isn't there.

The point of source code control, at least as CVS is designed to do it,
is to identify which people make which changes, and when they make those
changes.

What you say is true of any group of programmers all editing the same
source files in the same directory too.  Simple locking as done by some
editors can prevent one person from overwriting another's changes and
everyone will (or at least can) see everyone elses changes immediately
as they save them, just as your users can all see what each other have
done as soon as they "save" their changes to the database.

If you want to use CVS (or any other source code control system) then
you should know why you want to use it (and why you don't want to use
some alternative too).

CVS offers a whole suite of benefits and features beyond what you'd get
by just editing a bunch of files in a directory with some editor
interlock to prevent one person from clobbering another's changes.

In other words:  If you don't want private working directories for every
user then why are you using any kind of source code control tool in the
first place!?!?!?!?

(BTW, please don't quote the entire message you're replying to.  It's
not necessary -- you should quote only the minimum amount necessary to
give context to what you write.)

-- 
                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>