Flossie wrote:
snip...
2) I'm suprised how much CVS docs emphasise the fact that multiple users
can check out the same file and CVS can resolve conflicts as checkins
occur. However there are problems with letting users resolve conflicts
(they can get it wrong), and I doubt a system can be 100%
In her place, what I would do is:
1. Keep two local workspaces. One is the checkout from the remote repository, the other is the checkout from the local personal repository.
2. Do all my work in the local one, checking in as necessary.
3. When I release to the remote repository, I would copy all
The CVS client automatically handles the differences between Windows and UNIX line endings by converting the files when you do the checkout or update (or commit, or...). So, as unintuitive as it sounds, uncheck this option. Then you'll get the Windows line endings without those being imported
)
- Steve
prolist wrote:
But, isn't that option only about checkouts, what about check-ins I
can't locate any poption specific to that.
Thanks!!!
- Original Message -
From: Steve deRosier [EMAIL PROTECTED]
To: prolist [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 1
George,
Putting the repository itself on a networked drive (Samba or NFS or
others) is generally not recommended. Aparently there is a possiblity
with data loss. If you're running a server anyway, I'd just run CVS
from the same server and do the checkouts and such via the client-server
Again... this isn't going to tell you much. It basically gives you a
log of certain activity with the system. I can run the same command and
I get the following results:
* I have 21 modules checked out. Of those 21, I only have directories
in my sandbox for 15 of those (where did those
viewcvs -
http://viewcvs.sourceforge.net/index.html
It's what we use and we love it.
- Steve
Phil Labonte wrote:
Is there a web add-on that we can use to see who has checked out a given
module?
I know you can use the command line but I have some users that would
like to see who has checked
Scenario: N system admins. they checkout a machine's configuration into
their private working directory. they all are not currently root (or I'll
shoot them) and so the files are all owned by them with whatever default
mode per standard (umask etc) procedure. They do their edits, check them
into
Purushotham Komaravolu wrote:
Hi,
I am new to CVS administration.I need help in seting up the following.
1) Read only access to repository:
Developers ger read/write
access but QA and others get read-only access.
As an alternative, give
David,
Perhaps John could try this?
A suggestion to untangle:
1. Create a repository properly.
2. Copy the .v.v files into the repository manually.
3. Checkout the files into a working directory. (getting a .v file)
4. Copy the .v files manually into the repository.
5. Checkout the files into a
How about a script on a cron job that periodically (whatever granularity
you require from 1 minute to 1 day) checks to see if there's been any
new updates and if so does an update to the production tree? Seems
like a rather clunky work-arround, but it should at least get the
results you're
,
but I've found the interface implmentation of that to be a bit clunky
(it works well, but it's not always obvious what state you're in or how
to change it to the one you want).
- Steve
JacobRhoden wrote:
On Fri, 8 Aug 2003 08:40 am, Steve deRosier wrote:
We use ViewCVS and we love it. We use
We use ViewCVS and we love it. We use it for all sorts of things
including tracking the CVS repository and just viewing source files in
other projects (have you ever wanted a quick look or printout without
checking out the module and opening it in an editor?). For best usage
though, it is
If you're checking from an external box, don't forget to punch a hole in
the server's firewall if one is running. A firewall that we didn't
realize was running on our RH box tripped us up for a couple of hours.
- Steve
Kent Emia wrote:
port not running!!!
I ve checkec
Phil,
As you know, CVS doesn't version directories and frankly was never
designed with that in mind (never mind the argument over if it should or
should not, it simply doesn't). But...there is a program that does
record directory structure: tar. Perhaps you could somehow use tar in
, May 27, 2003 at 11:39:22 (-0700), Steve deRosier wrote: ]
Subject: Re: outsider's perspective
As you know, CVS doesn't version directories and frankly was never
designed with that in mind (never mind the argument over if it should or
should not, it simply doesn't). But...there is a program
No concurrent versioning system with a shared repository, and
particularly not one that can operate in a client/server mode, can ever
possibly make any use of ownership, nor even of most permissions bits.
Ownership information, and most permissions bits, MUST always be
specific to the client and
?
Basically, my current fix is to only use one method, ie only do my work
remotely using pserver.
Thanks,
- Steve
-Original Message-
From: Shankar Unni [mailto:shankar;cotagesoft.com]
Sent: Wednesday, October 30, 2002 11:35 AM
To: 'Steve deRosier'
Subject: RE: pserver login problem
than tried to get them to work together. Usually is a
great idea to make sure two parts work by themselves first. Who knew? :)
- Steve
-Original Message-
From: Kaz Kylheku [mailto:kaz;footprints.net]On Behalf Of Kaz Kylheku
Sent: Thursday, October 31, 2002 4:12 PM
To: Steve deRosier
be great.
Thanks,
- Steve
--
Steve deRosier
PianoDisc Design Engineer
(916) 567- ext. 175
www.pianodisc.com
[EMAIL PROTECTED]
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
20 matches
Mail list logo
