[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Obtaining the files modified/created after a failed/successful build
From: |
Mark D. Baushke |
Subject: |
Re: Obtaining the files modified/created after a failed/successful build of CVS repository |
Date: |
Fri, 12 Sep 2008 21:00:43 -0700 |
Spiro Trikaliotis <address@hidden> writes:
> For example, in my case, I use Windows as an additional server. That is,
> my main server is on a unixoid machine. However, when I am on travel
> with my laptop (without network access), I take an rsync'ed copy of the
> repository with me. This way, I can work offline (read-only!) with CVS
> as if I would have network access. Of course, I could use the :local:
> access method for this. However, I like to use CVS the same way as I use
> it with the real server, this, I am always using the :ext: access
> method. Additionally, if I go to another machine (and my laptop is
> around), I use that repository, too. So, in this case, I have to use
> :ext:.
Using :fork: is probably a better solution to your particular need. It
acts as client/server without needed to use rsh or ssh transport as
:ext: needs.
> ... - but, as we all know, some developers do not consider :pserver:
> to be a good idea at the first place, so, this might not be such a big
> restriction.
Yup. I still advocate that :pserver: should be removed or at least never
compiled by default... (The authentication business should be left to
the operating system and NOT poorly managed by a user-level program like
CVS.)
-- Mark
pgpgWLOEX617e.pgp
Description: PGP signature
- Re: Obtaining the files modified/created after a failed/successful build of CVS repository,
Mark D. Baushke <=