Quoting Alan Finlay ([EMAIL PROTECTED]):
I am in a bashing mood today. You are target, sorry.
> Sometimes waiting an hour
> or two and working on something else so the updates can be done
> sequentially can save the bother of a merge.
So, let me give you an example. One big file. Person A wo
On Wed, May 04, 2005 at 09:12:42AM -0600, Tobias Weingartner wrote:
> On Wednesday, May 4, "Alan Finlay" wrote:
> > I have done significant work with ClearCase and CVS in a software
> > development team environment, and some minor work with other revision
> > control tools. Team size for ClearCa
On Wednesday, May 4, "Alan Finlay" wrote:
> I have done significant work with ClearCase and CVS in a software
> development team environment, and some minor work with other revision
> control tools. Team size for ClearCase was around 20 developers, and with
> CVS around 10 developers. For an o
: "Roy Morris"
<[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 03, 2005 4:50 AM
Subject: CVS - Lock File
Our company has started to look at CVS as an alternative to our
current
products. When I suggested using CVS I was told not having a lock
file
or method of knowing who was work
s" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 03, 2005 4:50 AM
Subject: CVS - Lock File
Our company has started to look at CVS as an alternative to our current
products. When I suggested using CVS I was told not having a lock file
or method of knowing who was working on some code was g
Quoting Peter Valchev ([EMAIL PROTECTED]):
> > Have you looked at subversion? A colleague of mine is fanatical about it,
> > athough we don't use it here.
>
> You mean the one that has 23 build dependencies, and only compiles on
> i386? Hah.
That is the primary problem. The second problem is the
At 9:55 AM -0600 5/3/05, Peter Valchev wrote:
> Have you looked at subversion? A colleague of mine is fanatical
> about it, although we don't use it here.
You mean the one that has 23 build dependencies, and only compiles
on i386? Hah.
This sounds odd. I use subversion on FreeBSD/i386, FreeBSD/
At 09:55 AM 5/3/2005 -0600, Peter Valchev wrote:
> Have you looked at subversion? A colleague of mine is fanatical about it,
> athough we don't use it here.
You mean the one that has 23 build dependencies, and only compiles on
i386? Hah.
Didn't say *I* liked it, just that a colleague of mine preac
> Have you looked at subversion? A colleague of mine is fanatical about it,
> athough we don't use it here.
You mean the one that has 23 build dependencies, and only compiles on
i386? Hah.
On Tue, 3 May 2005, Marc Espie wrote:
> To expand on my prior message, CVS is missing some useful features,
> but locks is definitely NOT one of them.
>
Have you looked at subversion? A colleague of mine is fanatical about it,
athough we don't use it here.
I seem to recall that it address some of
espie:
> The main feature I'm missing is the ability to manipulate patchsets
> as an independent object. I often have several independent changes
> spanning several files, and there's nothing in cvs that allows me
> to select one change independently from the others, and not forget
> any file. Hav
To expand on my prior message, CVS is missing some useful features,
but locks is definitely NOT one of them.
The main feature I'm missing is the ability to manipulate patchsets
as an independent object. I often have several independent changes
spanning several files, and there's nothing in cvs tha
u're in an Oracle and/or UNIX shop, it should fit right in with how those
environments expect things to be done.
Thank you,
Mitch
-Original Message-
From: Roy Morris [mailto:[EMAIL PROTECTED]
Sent: Mon 5/2/2005 2:50 PM
To: misc@openbsd.org
Cc:
Subject:CVS - L
On Mon, May 02, 2005 at 09:10:00PM +0200, Marc Espie wrote:
> If you start running into conflicts, it usually means people don't commit
> often enough... and if they don't, it might be because intermediate code
> is not stable/does not compile, which bodes real bad for the project as
> a whole...
Roy Morris wrote:
Our company has started to look at CVS as an alternative to our current
products. When I suggested using CVS I was told not having a lock file
or method of knowing who was working on some code was going to be
unmanageable. (and nearly beaten to death, by the developers)
Since Open
Lock files don't replace good communication.
There are very little conflict issues in OpenBSD, considering the
developers cover the world, litterally.
A small projet where developers can talk to each other, live, shouldn't
have any problems, even without locks.
If you start running into conflict
* Roy Morris <[EMAIL PROTECTED]> [050502 14:59]:
> Our company has started to look at CVS as an alternative to our current
> products. When I suggested using CVS I was told not having a lock file
> or method of knowing who was working on some code was going to be
> unmanageable. (and nearly beaten
The entire idea behind CVS is to *not lock*.
The entire idea is that people write their own changes, then
collaborate on integration, out of band.
There is no locking, and there never will be.
Locking is used as an excuse by people who don't know how to communicate.
> Our company has started t
Our company has started to look at CVS as an alternative to our current
products. When I suggested using CVS I was told not having a lock file
or method of knowing who was working on some code was going to be
unmanageable. (and nearly beaten to death, by the developers)
Since Openbsd has the OpenCV
19 matches
Mail list logo
