CVS/notify is created by "cvs commit" (when unediting), "cvs edit", "cvs
release" (when unediting), and "cvs unedit". It's part of the client/server
protocol.
When using it in conjunction with "cvs add", it works fine under the normal
rsh-connect client/server setup. I don't know how it behaves under pserver.
Also, I don't know what'll happen in the following:
cvs add file
cvs edit file
cvs rm file
cvs ci # assuming other stuff has changed
Although I do know that:
cvs add file
cvs edit file
cvs rm file
cvs unedit file
will give you something like, "nothing known about..."
I hope this provides enough to track down the problem.
Noel
PS
One of my TODO's is to allow the editing and unediting of unknown files. Such a
patch should fix the above problem(s).
[EMAIL PROTECTED] on 2000.05.08 12:32:37
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: notify file in sandbox's CVS directory...
I have recently run into a rather odd instance of a notify file
causing problems in the CVS directory of a users sandbox... What I
would like to know is what might cause the creation of a notify file
in a users sandbox and what it's purpose is...
The problem started when a user was attempting to add files to the
repository, the pserver was reporting a 'nothing known about...' error
response.
Pertinent version info:
Client - jCVS 5.1.1, JRE1.2, win2K 2195, intel
Server - Redhat Linux 6.1 (sort of =), cvs 1.10.8, pserver, intel
The Notify file in CVSROOT is just comments, but watches are on for
the project...
The contents of the file are as follows:
--- begin paste ---
ESection_One.htm Thu Apr 13 14:07:23 2000 GMT remote.via.jCVS
./FuncSpec/SectionOne/
--- end paste ---
Is this a jCVS client issue, or does the c/s protocol require the
creation of such files? Any help would be appreciated as in the
future I would like to avoid whatever caused it... =)
Scott
--
Scott Sutherland National Computer Systems
(319) 354-9200 Measurement Services Division
[EMAIL PROTECTED] Iowa City, Ia
import my.standard.disclaimer.*; GO HAWKS!!!
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
