[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Ident lockup

From: Aaron Manning
Subject: RE: Ident lockup
Date: Wed, 18 Aug 2004 14:34:47 -0400

Sorry about that Aaron, I think my terminology is incorrect ;) Been working
in Linux for past few months, so been used to the RCS file being a link as
opposed to the windows file with a directory located in it. 

Our revision controlled source files are residing on a server on a local
>From there we check in/out files to our local machine. Since co/ci/rlog
etc... commands need to know where to search for the revision controlled
files, we created "RCS" text files which have the directory location in them
to where the code is stored on the LAN (our repository).

I attached an example of my "so called LINK file". 

If you just copy this file (or even create a totally blank file called RCS
<no extension>) and run Ident RCS & Ident rcs (for the PC running DOS/WIN
version) you'll see my issue on the "Ident RCS" command.

Again, sorry for the confusion.

-----Original Message-----
From: Aaron S. Hawley [mailto:address@hidden 
Sent: Wednesday, August 18, 2004 2:13 PM
To: Aaron Manning
Cc: address@hidden
Subject: RE: Ident lockup

I didn't fully process that your "RCS" file was a link.  Which DOS-based
operating system allows file links?  Is this some incarnation of Windows
NT(tm)? I only knew of file "shortcuts".

I tried looking for any specific checks for the file name "RCS" in Ident's
or RCS's source code, but nothing stuck out at me.

I used RCS installed on Debian GNU/Linux and I get a different message:

ident error: RCS: Is a directory

but I couldn't even find where in Ident's source code this error was being

a bit obscure, but interesting.

On Wed, 18 Aug 2004, Aaron Manning wrote:

> In my scenario, RCS isn't a directory, but an actual file.
> 10/20/2003  10:21 AM                69 RCS
> 08/18/2004  09:35 AM               414 tester.bak
> 08/18/2004  09:35 AM               414 tester.psp
> 08/18/2004  09:35 AM             7,119 tester2.bak
> 06/04/2004  09:05 AM    <DIR>          tester2.CS_
> 08/18/2004  09:35 AM             7,119 tester2.pjt
> 08/18/2004  09:35 AM             1,723 tester2.sbl
> Executing:
> C:\ident rcs
> rcs:
> ident warning: no id keywords in rcs
> C:\ident RCS
> <hangs... As if it's looking for further input>
> I wouldn't think that ident would care since windows (dos shell) is 
> case insensitive anyway. I'm thinking there is some case-sensitive 
> checking going on in Ident somewhere that is causing this.
> -----Original Message-----
> From: Aaron S. Hawley [mailto:address@hidden
> Sent: Wednesday, August 18, 2004 10:28 AM
> To: Aaron Manning
> Cc: address@hidden
> Subject: Re: Ident lockup
> As an addendum: on GNU/unix machines I observed this behavior:
> $ ident RCS
> RCS:
> ident warning: no id keywords in RCS
> $ ident rcs
> ident error: rcs: No such file or directory
> this is obviously a result of directories reading just like files on 
> GNU/unix but not on Windows.
> perhaps the windows(tm) source of RCS should check if the filename is 
> a directory.  this functionality is not crucial as there is no 
> directory recursion behavior anyway. /a
> On Wed, 18 Aug 2004, Aaron Manning wrote:
> > Hello All,
> >
> >      I have a question with the functionality of Ident. Currently I 
> > am using scripts to execute Ident on a list of files (100+). Within 
> > the files is the a link file called "RCS" pointing to the rcs 
> > repository. All files within the project are RCS'ed and when my 
> > script executes an "Ident.exe RCS" to check for $Id$ tags, Ident 
> > will hang. It is the same as if you just typed "Ident" with no file 
> > to check. I was wondering if this is intended or maybe this is a 
> > bug? I am using the RCS 5.7 Win version. I have verified that the 
> > linux version does not hang on an "Ident.exe RCS" call. Also, if I 
> > use "Ident.exe rcs" <lowercase> the hang issue does not occur? Has 
> > anyone else seen this?
> >
> > Thanks,
> > Aaron

Attachment: RCS
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]