François-Xavier Coudert <[EMAIL PROTECTED]> wrote: > I do only have small involvement in gcc, preparing few patches (never > more than 5 at a time) on limited areas (gcc/fortran, libgfortran and > gcc/testsuite), always on mainline or 4.0 branch. The way I manage to > keep mind sanity right now is to have a few complete trees (one for > 4.0 and 3-4 for mainline, each one with a local changes), called > gcc-newintrinsics, gcc-fpe, ... > Having 5 subversion trees will need much more space (for local > pristine copies), which I don't really have. Is there any way to force > subversion use one pristine tree for all modified trees, or is my way > of handling things completely rotten?
Not that I know of. As Daniel Berlin said, Subversion 1.4 will probably have support for checking out repositories with compressed local copies (or no copy at all -- but I wouldn't suggest this, as you'd start to be slow in "svn diff", "svn stat", etc). You may want to look into svk though, which implements a distributed system on the top of an exising subversion repository. svk working copies do not have a double-copy at all. Also I suggest you to look into "svn switch" which might be useful to you to switch an existing working copy from a branch to another, without redownloading the whole thing but just the differences. Giovanni Bajo
