We don't back up working copies at all. Since we try to keep the repository
fairly up-to-date from our working copies, we just do "svnadmin dump repos >
dump_nnnn" then "gzip dump_nnnn", and back that file up to CD-ROM or another
hard drive (it's recently become too large for a CD-ROM). Then, not only do
we save the latest committed version of the project, we also have all the
history.
****
**** --- Eric Wadsworth, 520-533-2749
****
> -----Original Message-----
> From: Neil Gunton [mailto:neil@nilspace.com]
> Sent: Tuesday, August 31, 2004 8:08 AM
> To: Ben Collins-Sussman
> Cc: users@subversion.tigris.org
> Subject: Re: Files changed on svn update
>
>
> Ben Collins-Sussman wrote:
> >
> > On Tue, 2004-08-31 at 09:53, Neil Gunton wrote:
> >
> > > That's an idea, it would certainly be a workaround. I
> guess I was just
> > > raising this as a possibly small thing for the svn
> developers that could
> > > be fixed if it turned out that it was trivial or a small
> programming
> > > oversight.
> >
> > It's not a trivial thing, nor an oversight. When you run
> 'svn up' at
> > the root of your working copy, every single object in your tree must
> > have its working revision "bumped" up to HEAD, even if the
> object didn't
> > change. That's why every single .svn/entries file gets edited. The
> > .svn/tmp directories change because that's where new
> repository files
> > are constructed, before they're merged/copied into the
> visible working
> > area.
>
> Ok, thanks! I'll just use the rsync exlude suggestion then.
>
> -Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 31 21:18:44 2004