[Top][All Lists]

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

RE: Exp state on top of dead

Subject: RE: Exp state on top of dead
Date: Mon, 4 Sep 2006 17:24:07 +0100

Hi Larry Et. Al.,

> From: address@hidden [mailto:address@hidden 
> Sent: 24 August 2006 18:20
> Cc: address@hidden; address@hidden
> Subject: Re: Exp state on top of dead
> CARTER-HITCHIN, David, GBM writes:
> > 
> > So the fix would be to manually resurrect it (by simply 
> moving it out of the
> > Attic?) then re-running the "cvs remove" command, so that 
> it goes back into
> > the Attic and gets status "dead" on the HEAD revision?
> If you just want to really kill it, there's no need to move it -- just
> get a working copy (either check out that specific file or do 
> an update
> with that file name in an existing working directory) then cvs remove
> and commit it.

In this particular instance we wanted to kill it, so thanks for your
suggestions.  I checked out the specific version, removed the sticky version
tag, rm'ed it and cvs removed it, and commited.  It now shows 'dead' on head
revision.  Let's hope it stays that way.

What worries me now is the possibility of there more files lurking out there
which are in the same state so I'm trying to write a little script to
identify them.    Note that validate_repo did *not* flag this as a problem,
even with -a switched on.  If run with -v, I can see 'dead' whizz by well
before 'Exp' later at HEAD, so it has the opportunity to catch this (author
cc'd in case [s]he's interested/has time to build this check in).  I thought
about modifying validate_repo, but then thought it might be easier to write
my own.

The problem I have is that I can't seem to do a 'cvs log' without checking
out the code.  If this script gets run as the repository owner, on the cvs
server machine, then I set the CVSROOT to :local:/path/to/repository and in
theory I'm set (?) but 'cvs log module/file' complains that there is no
module called 'module' 'here', even if i'm in the repository itself.
Obviously I want to avoid checking out the entire codebase to check things.
I could use a perl module to parse the raw RCS file, or write my own, but
I'd prefer to rely on native CVS commands.  Is there a way to achieve this?

Many thanks,

David Carter-Hitchin.
Royal Bank of Scotland
Interest Rate Derivatives IT
135 Bishopsgate

Tel: +44 (0) 207 085 1088

The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered 
Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 
This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The 
Royal Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 

reply via email to

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