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

RE: [TSVN] Severe performance degradation observed

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-12-13 20:06:59 CET

"Josha Foust" <jfoust@mankowindows.com> wrote on 12/13/2004 02:03:39 PM:

> -----Original Message-----
> From: Nicklas Norling [mailto:exinor@exinor.net]
> Sent: Monday, December 13, 2004 11:45 AM
> To: dev@tortoisesvn.tigris.org
> Subject: Re: [TSVN] Severe performance degradation observed
> > Mark Phippard wrote:
> >
> > >Have you checked the same timestamp issue that you suggested to
> > >else? I imagine if you did a clean checkout that would be a way to
> > >
> > >Mark
> > >
> > Yes, my WC is a fresh check out with no updates or commits (it's a
> > repo). There should be no date
> > issues unless there is a bug in subversions date writing.
> > /Nicke
> I just did a fresh checkout and I get the current date/time unless "set
> filedates to the "last commit time"" is checked. Which is reasonable,
> you have to make sure that is set when you do your fresh checkout.
> I don't have any build tools that depend on the timestamp, so I leave it
> permanently. But might be nice as a property for different projects. :)

That is a different issue. What we are talking about is that the WC
stores the timestamp of the files you checked out, regardless what they
are. When it scans the WC for changes, if the timestamp is not changed it
just assumes the file is unchanged - which performs nicely.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 13 20:07:32 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.