info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Do most people checkout read-only and use "cvs edit"?


From: Mark D. Baushke
Subject: Re: Do most people checkout read-only and use "cvs edit"?
Date: Wed, 07 Jul 2004 11:21:44 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

'cvs edit' and 'cvs watchers' is something that was bolted on to cvs as
a way to give advistory locking to cvs for files that are difficult to
merge.

In general, I never use it (other than to test that the feature still
appears to work).

I would guess that very few people will use it unless they have binary
files or files that require very close cooperation to edit which makes
it hard to use in the full 'concurrent' model that gives CVS its name.

Your mileage may vary...

        -- Mark

Karr, David <address@hidden> writes:

> I have a question about how people use CVS.  How common is it to always
> checkout and update read-only, and then use "cvs edit" when you start
> working on a file?  Or, do people checkout read-write and never use "cvs
> edit"?  I have always thought that modules should be checked out
> read-only, and "cvs edit" is only used when you start to work on a file.
> However, I'm getting the impression that that appears to be an
> "alternative" strategy, and even deemphasized.
> 
> In fact, in the WinCVS interface, the "cvs edit" functionality is under
> the "Trace" submenu, hiding it from the first-level menu.
> 
> Other SCMs use the strategy that I'm used to as the primary strategy
> ("checkout" read-only, and do a specific operation to put the file into
> edit mode).
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA7D843x41pRYZE/gRAve5AJ0XOKiTDQJCDOI2m3U0oKmJUTAPKwCg1LbY
OxLBVuRUqUZvODqHPdHByKU=
=15DI
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]