Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!rhesus!uwmacc!uwmcsd1!lakesys!gryphon!cadovax!keithd
From: keithd@cadovax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Cp: A replacement for AmigaDos Copy
Message-ID: <1578@cadovax.UUCP>
Date: Mon, 1-Jun-87 20:22:23 EDT
Article-I.D.: cadovax.1578
Posted: Mon Jun  1 20:22:23 1987
Date-Received: Thu, 4-Jun-87 02:28:20 EDT
References: <741@van-bc.UUCP> <121@gtss.UUCP> <156@l5comp.UUCP> <3171@well.UUCP>
Reply-To: keithd@cadovax.UUCP (Keith Doyle)
Distribution: na
Organization: Contel Business Systems, Torrance, CA
Lines: 22

In article <3171@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>	When you invoke "Copy", you make a copy of the file in question.  It
>is *NOT* the same file.  The only thing similar between them is their
>contents.  By copying the source file, you *create* a totally *new*
>destination file.  When creating a new file, it gets the current date.
>Thus, you aren't modifying anything.  You are creating a new file (with
>today's date), and filling it with the contents of the source file.

It all depends on what you consider a files 'date' field as,
'last modified date' or 'last copied date'.  I'd prefer a filesystem
that provides BOTH date fields.  'Last modified date' can be an indication 
of 'version', while 'last copied date' can be an indication of when the 
file was backed up.  On a backup disk where all of the files were
backed up at the same time (the way I usually backup files), EVERY files
'last copied date' is the same, and the same as the disk's last used
date.  In such a case, and with only one choice of 'date' fields, I
prefer using 'last modified date' as an indication of version, as
'last copied date' is more usually redundant information.
  
Keith Doyle
#  {ucbvax,ihnp4,decvax}!trwrb!cadovax!keithd
#  cadovax!keithd@ucla-locus.arpa  Contel Business Systems 213-323-8170