Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!rpi!leah!wfh58
From: wfh58@leah.Albany.Edu (William F. Hammond)
Newsgroups: comp.sys.amiga
Subject: Re: cp-mv-rm1.1 command substitute
Message-ID: <3431@leah.Albany.Edu>
Date: 31 Jul 90 21:50:15 GMT
References: <2666@mindlink.UUCP>
Reply-To: wfh58@leah.albany.edu.UUCP (William F. Hammond)
Organization: Dept of Math & Stat, SUNYA, Albany, NY
Lines: 26

In article <2666@mindlink.UUCP> a218@mindlink.UUCP (Charlie Gibbs) writes:
>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
>> ...
>>   much better (don't you agree?)
>     No, I don't.  The main reason I stick with Matt Dillon's Shell2.07m
> ...
>Perhaps the best solution would be to have an environment variable to
>determine the default action of any copy (are you listening, Commodore?).
> ...
>Charlie_Gibbs@mindlink.UUCP

I've been a very happy datestamp fanatic since the time of the ARP 1.1
release (early '88, I believe) when I was able to use the environmental
variable "copyflags" to govern the behavior of ARP's "copy" with regard
to datestamps.  The 1.3 release of ARP offers the possibility of
controlling 5 switches on the "copy" command with this environmental
variable.

And the price can't be beat.

----------------------------------------------------------------------
William F. Hammond                   Dept. of Mathematics & Statistics
518-442-4625                         SUNYA, Albany, NY 12222
wfh58@leah.albany.edu                wfh58@albnyvms.bitnet
----------------------------------------------------------------------