Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!van-bc!rsoft!mindlink!a218
From: a218@mindlink.UUCP (Charlie Gibbs)
Newsgroups: comp.sys.amiga
Subject: Re: cp-mv-rm1.1 command substitute
Message-ID: <2666@mindlink.UUCP>
Date: 29 Jul 90 20:25:19 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 18

In article <1035@tau.sm.luth.se> d88-mbe@sm.luth.se (Michael Bergman)
writes:

>4. The cp command has date CLONE as default. This should be the other way
>   around: you shouldn't have to use `cp -n File1 File2` to get a fresh
>   date on the new copy. `cp -o File1 File2` to retain the old date is
>   much better (don't you agree?)

     No, I don't.  The main reason I stick with Matt Dillon's Shell2.07m
is that its cp command assumes CLONE by default.  I'm a date-stamp
fanatic; I depend on them for program version control, and so does make.
Perhaps the best solution would be to have an environment variable to
determine the default action of any copy (are you listening, Commodore?).

     Just another chance to harp on my pet peeve...

Charlie_Gibbs@mindlink.UUCP
"Oh, shit!"  "We're all in it together."  -- Brazil