[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: MTime resurrected

From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 17 Feb 2012 10:34:54 +0100

> -----Original Message-----
> From: Fuhrmann Stefan (ETAS/ESA1) [mailto:Stefan.Fuhrmann_at_etas.com]
> Sent: vrijdag 17 februari 2012 9:27
> To: dev_at_subversion.apache.org
> Cc: rick_at_longbowgames.com; peter_at_p12n.org
> Subject: Re: MTime resurrected
>
> Peter Samuelson <peter_at_p12n.org> wrote:
> > Now do a 'svn update' or 'svn switch' which changes foo.c.
> >
> > Current svn: foo.c mtime is set to the present time. It is now newer
> > than foo.o. [Of course you can set foo.o's mtime in the future, but
> > that's just breaking things _on purpose_.]
>
> Ahem. At least with 1.7+ (and probably for a long time
> before that), a c/o or update sets ctime=atime=now
> and mtime will be set commit time. I.e. make *will*
> break if you update to older revisions.

No, by default it does not.

You only get this behavior if you enable use-commit-times in your Subversion
configuration.

        Bert
Received on 2012-02-17 10:35:42 CET

This is an archived mail posted to the Subversion Dev mailing list.