-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 10, 2005, at 8:26 AM, Peter Valdemar Mørch wrote:
> 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.
snip...
> 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 differences?
>
> What is *the method* of getting a pristine checkout from a possibly
> dirty working copy?
Just a stab at this...
svn revert -R .
svn update
- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFB4rDVzaKkuvKwKvcRAgyHAKCGahGp+I/wM4Q8qA2Xq2n7s2LnHwCeJYz9
ku44t9yO3Gr/o3VxI+TkuQk=
=Tgp7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 10 18:00:16 2005