Set  the  RCS  file's  modification time to the new revision's time if the former precedes  the  latter and  there  is  a  new  revision;  preserve the RCS file's modification time otherwise.   If  you  have locked  a  revision,  ci  usually  updates  the RCS file's  modification  time  to  the  current  time, because  the  lock  is  stored  in the RCS file and removing the lock requires changing the  RCS  file.  This  can create an RCS file newer than the working file in one of two ways: first, ci -M can create  a working  file  with a date before the current time; second, when reverting to the previous revision the RCS  file can change while the working file remains unchanged.  These two  cases  can  cause  excessive recompilation caused by a make(1) dependency of the working file  on  the  RCS  file.   The  -T  option inhibits  this recompilation by lying about the RCS file's date.  Use this option  with  care;  it  can suppress  recompilation  even when a checkin of one working file should  affect  another  working  file associated  with  the  same RCS file.  For example, suppose the RCS file's time is 01:00, the (changed) working  file's  time  is 02:00, some other copy of the working file has a time of 03:00, and the  current  time  is  04:00.   Then ci -d -T sets the RCS file's time to 02:00 instead of  the  usual  04:00; this causes make(1) to think (incorrectly) that the other copy is newer than the RCS file.



































































































































































































Previous  |  Next ]     [ Up  |  First  |  Last ]     (Article 166 of 485)
 
Comments, flames, broken links?
Please send email to maintainer@intricate-simplicity.com