> Better don't use absolute paths. Absolute paths make little sense because,
> in general, the location of your local workspace is unrelated to the
> repository location.
if I don't use absolute paths, then the cvs commands do not work like I need
them to. For example, if I run a checkout command from c:, then the files
get put on the c drive. Then, let's say I run a log command (w/o the
absolute path) from the d: drive to see the revision history of a file. It
can't find the file, since the checkout command put them on the c drive...,
but it's looking on the d: drive. The only way that I have found to get
around this is to use absolute paths, and tell the log command that i'm
looking for a file on c:. Are there better ways to get around this, or was
CVS not made for that kind of usage?
> Please, don't do this. With this command line your client is directly
> working with the repository, bypassing the CVS server.
So your saying that unless I go through a pserver, ntserver, or some other
kind of 'gateway' (is there a better term to describe them?), that I'm not
actually using the CVS-NT server mechanisms? Wait a minute... I just had a
vision... is the CVS-NT server actually the pserver/ntserver? If so, then
the CVS-NT server just provides authentication, correct? maybe this is
making a little more sense (assuming the above sentence is correct,
otherwise i'm still lost :)).
-matt
There is lots of documentation available about CVS in general (e.g.
(http://cvsbook.red-bean.com/ and http://www.cvshome.org/docs/), and cvsnt
specificly (e.g. http://www.devguy.com/fp/cfgmgmt/cvs/cvs_admin_nt.htm
and http://www.cvsnt.org).
Joachim
--
work: [EMAIL PROTECTED] (http://www.netacquire.com)
private: [EMAIL PROTECTED] (http://www.kraut.ca)
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
