Re: old fileattr files - safe to delete?

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

CARTER-HITCHIN, David, GBM <address@hidden> writes:

> We've got a bunch of CVS/fileattr files in our repository that are ancient.
> I think I'm right in saying that the only way that these get created are
> when people run 'cvs watch' and 'cvs edit'.  The people who did this have
> long since gone and so have their logins.  Is it safe to just delete the
> fileattr files to get rid of the watches or is there an official way?

The CVS/fileattr files are there to do book keeping on advisory locking
and 'cvs watch' files. You should be able to remove any of those files
without hurting the correct operation of the repository. So, yes, it is
safe to just delete the fileattr files.

When cvs 1.12.14 comes out, there will be a way for a cvs 'admin'
to remove specific user locks or watches from specific files. I do
not believe there is any command to just find all of them and purge
a specific user that has had their login removed.

        -- Mark

PS: A brief note about your dislaimer:

> ***********************************************************************************
> The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered 
> Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
> Authorized 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. 

This disclaimer is really silly when sent to a public e-mail list. Your
message is in a number of different archives and will be unlikely to be
deleted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEdKL4Cg7APGsDnFERAi3yAKCSFkQmwruE/B5D1ruBFhgcGg0SPACfQpR9
tWCbIrBQnYB5v+Cd0TDsBjQ=
=svp3
-----END PGP SIGNATURE-----