Please use Reply to All to keep replies on the list.
On 10/13/06, Phyrefly <phyrefly.phyre@gmail.com> wrote:
> > Kevin covered pretty much everything, but I have a followup question
> > here Phyrefly. Why do you think there is a "lot of overhead" when
> > updating a project that's part of a larger repository? If a developer
> > only needs one or two particular small projects, then that's all they
> > should check out and all they need to update. In this scenario, there
> > are only very rare cases where one would need/want to check out the
> > whole repository.
>
> This comes from the question I asked about getting a post-commit
> script to update just one project, rather than the whole repo. If
> that's possible, then yes, the overhead becomes less of a problem. If
> not, then it would start to be a problem when a one-file change forced
> a 300MB repo to update an entire working copy.
svn update updates the current working copy. Wherever you've checked
out the directory from, it goes back to that URL and pulls down
updates from there. So if you check out a single project out of 500
in one repository, then svn up run from within that one project's
working copy will only update that project.
If you haven't yet, check out The Book, http://svnbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 13 14:55:48 2006