Segmentation Fault (was Re: CVS sticky information ignored on import)

Thanks Greg. 'cvs import' does not work from within a working directory (aka sandbox) -- i.e. it does not do anything special. Or rather it only works by virtue of the fact that by default it'll ignore all the administrative CVS sub-directories and the files they contain. Ah, the

Re: problem with pserver

Hi, Unless the '/cvs_repository' in $CVSROOT is '/home/cvs/prj', your connection will be refused in this way (because of the --allow-root argument to cvs pserver). HTH, Hamish Grzegorz ?y?a [EMAIL PROTECTED] wrote in message news:a8ugsu$o47$[EMAIL PROTECTED]... hi. I have a problem, when i

CVS sticky information ignored on import

Hi, I'm a newcomer to CVS so please forgive me if the answer to this question is obvious. I have tried to find an answer in the FAQs and the Cederqvist but without success. It seems to me that if a file is marked as binary or tagged in CVS/Entries in a sandbox, e.g.: /noodle.jpeg/1.1/Mon Apr 8