Barak A. Pearlmutter wrote:
Didn't mean to cause trouble - my thought was to make it easier, via a
miniscule amount of documentation, for people to transition without
getting burnt. After all, since cvsnt is active etc, it would be good
to transition everyone off tired old cvs and onto shiny new
Barak,
> Didn't mean to cause trouble - my thought was to make it easier, via a
> miniscule amount of documentation, for people to transition without
> getting burnt.
If you'd like to contribute to the wiki then please create yourself a
username and then post a request to the CVSNT newgroup req
Didn't mean to cause trouble - my thought was to make it easier, via a
miniscule amount of documentation, for people to transition without
getting burnt. After all, since cvsnt is active etc, it would be good
to transition everyone off tired old cvs and onto shiny new cvsnt.
I guess I'd say that
This is an edited copy of the e-mail I sent to Andreas on 30th June
2008.
This bug 466408 is not debian specific - and I think that the correct
course of action would be to point the user to the CVSNT newsgroup.
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.c
Thanks for such a quick and helpful answer!
> ... you have to define your repository configuration in the file
> /etc/cvsnt/PServer
That solves the problem for *me*, because it is my own machine.
But a followup question does come to mind.
What if someone with a user account, without root acces
Barak A. Pearlmutter wrote:
Package: cvsnt
Version: 2.5.03.2382-3
I have a machine MY_CVS_SERVER_HOST running cvs (1:1.12.13-8) with a
repository in /home/cvs and clients accessing it via SSH.
I upgraded a client from cvs (1:1.12.13-8) to cvsnt (2.5.03.2382-3),
and everything worked fine: cd
6 matches
Mail list logo
