Re: disjoint working copies and single commit

On May 22, 2006, at 18:16, Dimitri Papadopoulos-Orfanos wrote:

> [snip] Now the problem is that users don't have enough room on
> their account to check out *all* projects. They still need to
> checkout *many* projects, and they also need to commit atomic
> changes to these different projects. The projects are indeed
> loosely related, but they're still related; for example an API
> change in project001 might imply changes in project002, project005
> and project456, and these changes are directly related to the
> change in project001, so we would like a single commit for all
> these changes.
>
> How would you handle this situation? Is there any solution I'm
> missing? Would you reorganize the project layout in the repository?
> How?

This is an answer:

http://svn.haxx.se/users/archive-2005-12/0657.shtml

It does require you to have enough disk space for the initial
checkout though. The disk space is then reclaimed in a second step.

If that won't fly, you can always check out with the -N switch, but
it is broken; there is a bug open on that. It may work well enough
for you, or it may be too broken to use; you could try it out.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 22 19:00:57 2006