Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ucla-cs!sdcrdcf!trwrb!wiley!bob
From: bob@wiley.UUCP (Bob Amstadt)
Newsgroups: comp.sys.atari.st
Subject: Re: PD C_compiler & Csh
Message-ID: <478@orville.UUCP>
Date: Sun, 19-Apr-87 13:03:35 EST
Article-I.D.: orville.478
Posted: Sun Apr 19 13:03:35 1987
Date-Received: Sun, 19-Apr-87 23:46:27 EST
References: <387@sbcs.UUCP> <1935@ihuxy.ATT.COM> <859@viper.UUCP>
Organization: TRW Inc., Redondo Beach, CA
Lines: 20
In-reply-to: john@viper.UUCP's message of 17 Apr 87 19:10:08 GMT

Posting-Front-End: GNU Emacs 18.36.2 of Mon Feb 23 1987 on orville (berkeley-unix)


In article <859@viper.UUCP> john@viper.UUCP (John Stanley) writes:

>     One important thing I'd like to see -all- shell writers do is to get
>   the old date and time properly transfered to the new file.  It's not
>   very complicated (takes about 5 lines of C) and makes the copy function
>   -much- more useful...  (Ever try using MAKE in a system where copying
>   your files flakes out the date and time info?  It doesn't work...!   :(

I disagree. It is very important copy updates the date to the current date
and time. Example: I make some changes to a file which later proves to be
damaging or useless. I get back the original source from a backup. This
constitutes a change and therefore should affect the last modified date.
If you are using MAKE, then you shouldn't move your files (at least not
very often).

		Bob Amstadt

		bob@wiley.uucp (UUCP)
		trwrb.uucp!wiley!bob (Alternate UUCP)
		csvax.caltech.edu!wiley!bob (Alternate UUCP or ARPA)