[Cvsnt] Timestamp of files from checkout

[MHO]

Bo is correct.  I was mistaken.  As he and others have pointed out, the
timestamp is set to the first time the files are imported.   I still believe
that this is a bad default behaviour for import.  What happened was this:  I
checked a large existing project into CVS.  All the original file timestamp
information was lost and the timestamps were set to the date of the first
import.   A lot of information was lost.  When a file is first imported into
a module the timestamp of the file should be kept intact.  The whole point
of having a version control system is to preserve information about a
project.  Throwing out valuable info in its first step seems wrong.  What
makes matters worse is that there doesn't even seem to be an option to
preserve file timestamp.

-Scott

"Bo Berglund" <bo.berglund at telia.com> wrote in message
news:3c165b74.673839439 at news.cvsnt.org...
> On Tue, 11 Dec 2001 17:02:36 +0000 (UTC), "MHO" <scott at mho.net> wrote:
>
> >Well, when I do a "cvs checkout" of my module, all the files are given
the
> >current date and time.  Not the date and time they were last modified.
> >
> >-Scott
> >
> No, you are not right.
> I just doublechecked this statement since I think that I did not
> recall seeing this behaviour. So I checked out a test module from my
> own CVSNT server using WinCvs (1.10.8 and 1.2 respectively).
> The files come out with timestamps 2001-10-20 which is the date of the
> last commit on that module. Today is 2001-12-11, so it is not using
> today's date.
>
> /Bo
>
>
> _______________________________________________
> Cvsnt mailing list
> Cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt


_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt