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

Re: Performance Question

From: Peter Valdemar Mørch <nospam_at_morch.com>
Date: 2005-01-10 17:26:46 CET

Ben Collins-Sussman wrote:
> On Jan 10, 2005, at 8:58 AM, Hari Kodungallur wrote:
>> Currently, our daily/nightly build (not individual developers) does
>> fresh checkout everyday. The repository is rather large and hence the
>> concern.
> That's still inefficient. The build system should run 'svn update' on
> the same working copy every night. That's what most of the rest of us do.

I'm with Hari on this one. Daily / official builds should start with a
pristine copy of the module that is about to be compiled, ensuring that
there are no local files and/or modifications.

Yes one could start with a `svn status` to see if there are any local
files or modifications, but then there is svn:ignore.
One could then use `svn st --no-ignore`. What other things might bite?

It does bring up an interesting question: If the output of
`svn st --no-ignore`
   after an
`svn update`
is completely empty, is it then guaranteed in all cases that "." will
equal what one gets with a fresh checkout, so that

`diff -r . ../newcheckout`

is empty?

Are there other things that could be overlooked? E.g. keyword expansion

What is *the method* of getting a pristine checkout from a possibly
dirty working copy?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 10 17:32:57 2005

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

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