Timestamps on workfiles

2003-01-27 Thread Kenneth Porter
I'm about to switch to CVS from PVCS. I've been using a flag for PVCS to touch workfiles when I get changed ones from the repository. (For PVCS users, I use get -u -t *.??v to get updated files and touch them.) This ensures that my build process will rebuild the binaries that depend on those

Re: Discouraging :local:

2003-01-27 Thread Kenneth Porter
--On Saturday, January 25, 2003 2:42 PM -0500 Greg A. Woods [EMAIL PROTECTED] wrote: The latter, the sharing part, is where the real trouble begins. Ensuring reliable order of operations for various operations which would be atomic on a local filesystem is very very difficult (literally

Restoring repository on basis of backup

2003-01-27 Thread Jarl Friis
Hi. I am new to the list, so please be gentle. I had a disk-crash. But I happend to save the home partition. I have a rather old backup of the CVS repository that I have now reestablished plus a more recent versions of some directories checked out of the CVS prior to the crash. I now want to

Re: Timestamps on workfiles

2003-01-27 Thread david
I'm about to switch to CVS from PVCS. I've been using a flag for PVCS to touch workfiles when I get changed ones from the repository. (For PVCS users, I use get -u -t *.??v to get updated files and touch them.) This ensures that my build process will rebuild the binaries that depend on

Re: Restoring repository on basis of backup

2003-01-27 Thread bollu
How can I easily make my CVS repository up-to-date only loosing the history information between time of backup and now (working revision)? I think you have to manually cvs add all the files that are in your working directory but not in the CVS repository. Then cvs commit your working directory.

Deleting branchs

2003-01-27 Thread Federico Vaca \( I \)
Hi, We created a branch BRANCH_VX_XX_A_X_FISCAL by error in our project an we need to delete this branch (permanently) ... How can i do this ? , Wich steps need to follow ? Thanks in advance ... Atentamente, Ing.Federico Vaca Líder de Proyecto Área de Desarrollo [EMAIL PROTECTED]

cvs update lag

2003-01-27 Thread jhughes
We are seeing major lag when issuing cvs update . in the root dir. of any of our dev's checkouts. (Major lag as in 5 mins. or MORE) A trace shows a long wait @ - unlink_file(CVS/Entries.Log). Our CVS server is FreeBSD. The main clients are Solaris and Linux. Any clues/hints/pointers of

Help Required:

2003-01-27 Thread Amit Sharma
Hi, Is there any way to findout with one command for all the watches that have been applied in the whole repository. P.S.: I have an idea that there is a file called fileattr which stores all the information for the watch but I don't want to look for each fileattr to look for the user's

starting with an empty repository

2003-01-27 Thread CHARLES HART, BLOOMBERG/ 499 PARK
Maybe it's me and not cvs 1.11.2 ... I think the following command sequence should work... $ mkdir workarea $ cd workarea $ cvs checkout -l . $ touch file0 $ mkdir module $ touch module/file2 $ cvs add module/file2 ... I am looking for a command sequence to get file2 into CVS without first

starting with an empty repository (more)

2003-01-27 Thread CHARLES HART, BLOOMBERG/ 499 PARK
I made some progress... $ cvs checkout -l . $ touch file0 $ mkdir module $ cvs add module $ touch module/file2 $ cvs add module/file2 The module itself needs to be added to then get the file in. Further, if I don't want ALL of the files in the repository root, (caused by the initial check out),

Re: Help Required:

2003-01-27 Thread Riechers, Matthew W
Amit Sharma wrote: Is there any way to findout with one command for all the watches that have been applied in the whole repository. 'cvs watchers' should do what you want. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED]

Re: Restoring repository on basis of backup

2003-01-27 Thread Eric Siegerman
On Mon, Jan 27, 2003 at 12:33:08PM +0100, Jarl Friis wrote: I had a disk-crash. But I happend to save the home partition. I have a rather old backup of the CVS repository that I have now reestablished plus a more recent versions of some directories checked out of the CVS prior to the crash.

Re: starting with an empty repository (more)

2003-01-27 Thread Larry Jones
CHARLES HART, BLOOMBERG/ 499 PARK writes: The module itself needs to be added to then get the file in. Further, if I don't want ALL of the files in the repository root, (caused by the initial check out), the solution seems to be name one file rather than .. -CTH Most people don't put files

Re: Discouraging :local:

2003-01-27 Thread Greg A. Woods
[ On Monday, January 27, 2003 at 02:48:59 (-0800), Kenneth Porter wrote: ] Subject: Re: Discouraging :local: --On Saturday, January 25, 2003 2:42 PM -0500 Greg A. Woods [EMAIL PROTECTED] wrote: The latter, the sharing part, is where the real trouble begins. Ensuring reliable order of

Re: Timestamps on workfiles

2003-01-27 Thread Kenneth Porter
--On Monday, January 27, 2003 8:07 AM -0600 [EMAIL PROTECTED] wrote: When CVS checks out files, it uses the repository timestamp. When it updates, the changed files get the current timestamp, and so are in effect already touched. This is normally the desired behavior. For example, if you

Re: Discouraging :local:

2003-01-27 Thread Kenneth Porter
--On Monday, January 27, 2003 6:20 PM -0500 Greg A. Woods [EMAIL PROTECTED] wrote: As far as I know samba has no locking protocol (I don't think the underlying SMB protocol has locking either, but I may be mistaken). There's something called an opportunistic lock or oplock, opportunistic to

Re: cvs update lag

2003-01-27 Thread Mark D. Baushke
[EMAIL PROTECTED] writes: We are seeing major lag when issuing cvs update . in the root dir. of any of our dev's checkouts. (Major lag as in 5 mins. or MORE) A trace shows a long wait @ - unlink_file(CVS/Entries.Log). Our CVS server is FreeBSD. The main clients are Solaris and Linux.

Re: Discouraging :local:

2003-01-27 Thread Fabian Cenedese
Well, generically speaking Ethernet's FCS field is a 32-bit CRC of the whole data frame. However if I understand the math correctly that means that only 32-bit or shorter errors (remember Ethernet is serial) can be detected reliabliy and only about 99.955% of error bursts longer than 32