Wait a second... Let me try to explain what I mean:
tjk@thor:~/type1> ls -l foofoo
-rw-rw-r-- 1 tjk prg28 Apr 17 17:11 foofoo
tjk@thor:~/type1> cvs ci -m test foofoo
Checking in foofoo;
/work/ptg/cvsroot/type1/foofoo,v <-- foofoo
new revision: 1.4; previous revision: 1.3
do
Tom Kacvinsky writes:
>
> The source is from the FAQ distributed with the CVS 1.11 source (and the text
> is the same in the CVS FAQ-o-matic maintained by Pascal Molli):
[...]
> The line that I am referring to is this one:
>
>The "commit" command retains the timestamp of the file, if the act
Tom Kacvinsky writes:
>
> According to the
> documentation I have read, the file should have the modification time
> of when the file was checked in. Instead, it has the time of check in.
Could you provide a complete citation, please? As far as I can see, CVS
has never used t
Hi Larry,
The source is from the FAQ distributed with the CVS 1.11 source (and the text
is the same in the CVS FAQ-o-matic maintained by Pascal Molli):
9. Why do timestamps sometimes get set to the date of the revision,
sometimes not? The inconsistency causes unnecessary recompiles.
Th
I think this might be a duplicate... Sorry if it is.
Submitter-Id: net
Originator: Tom Kacvinsky
Organization: American Mathematical Society
Confidential: no
Synopsis: Timestamps in master files are wrong upon check in.
Severity: serious
Priority: medium
Category:
