[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Consistency check of repository & knowing whether files are being wa
Re: Consistency check of repository & knowing whether files are being watched
Wed, 19 May 2004 11:20:20 +0200 (CEST)
> Nothing comes to mind, but it has been a long day... have you considered
> a file that has only been added to a branch or removed from the mainline
> (it will be in the Attic/ directory).
well, I considerd the Attic/ as a subdir of the repository as all the
others. The script could iterate through it as usual. But I see that I was
wrong. The attic doesn't have a fileattr! So it's not so easy.
That's the kind of snare I expected! :)
So, I guess, the processing of the Attics would require a parsing of the
,v-files, since I assume the watch or edit information there. But perhaps
I am mistaken. Is it possible to remove a file which is still watched or
edited. I guess at least the latter should be impossible. Or is the
information about watches/edits lost in such a case? Anyway, those files
wouldn't be so important anyway, since they belong in principle to trunks
which have state 'dead', right?!
That brings me to the question how can I get information via cvs about
files being held in attics?
Also I do not know what happens if you have several watches on more than
one revision of a file... Have to test, but expect that to be simply
appended to the according line in the fileattr file together with
information which revision is actually in focus.
OK, still collecting all these thoughts to get an idea what I have to take
care of, since I do not really want to screw up my repositories with a bad
designed tool... Looks like it's not so easy to set it up.