[ On Friday, October 12, 2001 at 11:21:03 (GMT), Bryon Lape wrote: ]
> Subject: Re: Making a file writeable
>
> Freedom? What freedom? Is it not source "control" or is it source "freedom"?
> One is free to more easily and quickly lay waste to another's wor
[ On Thursday, October 11, 2001 at 23:16:48 (-0600), James Knowles wrote: ]
> Subject: Re: Making a file writeable
>
> I guess it's like freedom. Freedom scares the living daylights out of people
> conditioned to living under tight controls.
Very good point.
Some (many? m
The problem is that you have multiple developers modifying the same area of
code without communicating with each other.
The way that you haven't solved that problem in the past is to not allow
two developers to be able to modify the same source file at the same time.
That costs you time when the
>Then spend time doing the merge by hand and having to
>possibly to ahold of the programmer who made other changes to make sure
everything
>is done correctly. Now two programmers, at least, are being unproductive
and
>costs are going up.
Don't you have regression tests to check if you've broke
Freedom? What freedom? Is it not source "control" or is it source "freedom"?
One is free to more easily and quickly lay waste to another's work, but that's
hardly an improvement.
CVS smells just like what it is, an acedemic exercize. I've used all manner of
them over the years: PostgreSQL, Ha
> In a sane and normal source control
> system,
Do you mean a "we can't figure out how to implement parallel development so
we'll put a straightjacket on our customers and convince them that it's
superior" source control system?
> files stay read only until you check them out.
Bad Bad Bad B
[ On Wednesday, October 10, 2001 at 00:59:20 (GMT), Bryon Lape wrote: ]
> Subject: Re: Making a file writeable
>
> This only works on the first checkout. In a sane and normal source control
> system, files stay read only until you check them out. CVS seems to be
> neither and let
This only works on the first checkout. In a sane and normal source control
system, files stay read only until you check them out. CVS seems to be
neither and lets people change files at will. This is quite bad and counter
productive.
[EMAIL PROTECTED] wrote:
> > When a Linux user goes a check
PROTECTED]
Subject: Re: Making a file writeable
> When a Linux user goes a checkout of a module, all the files are
> writeable and they stay that way even after a commit. When a Windows
> user, however, does a checkout via WinCVS, all the files are read-only.
> Is there a way
> When a Linux user goes a checkout of a module, all the files are
> writeable and they stay that way even after a commit. When a Windows
> user, however, does a checkout via WinCVS, all the files are read-only.
> Is there a way to make them writeable via WinCVS? Also, when the files
> are
When a Linux user goes a checkout of a module, all the files are
writeable and they stay that way even after a commit. When a Windows
user, however, does a checkout via WinCVS, all the files are read-only.
Is there a way to make them writeable via WinCVS? Also, when the files
are comitted, they
11 matches
Mail list logo
