> From: Karl Fogel
>
> And the sparse-directories support can happen in two stages anyway:
>
> - In 1.5, ship the new APIs, with (at a minimum) equivalent
> functionality to what we have today with -N. Ideally, we'll also
> have some of the new features described in README.branch, but we
> probably won't have all of them. Heck, some of them remain to be
> spec'd :-).
Just to add my (non-binding) +1 support for sparse directories as soon
as humanly possible. I work with a distributed team using multi-gigabyte
repositories, unfortunately large parts of the repository tree are often
not required by quite a few in the team. Currently, selectively checking
out parts of the tree is the only option, but it does tend to be rather
messy and error prone. Sparse directories would be a dream come true for
us.
Merge tracking would certainly be very useful, but I for one don't want
to see it hold up a host of other useful features.
Cheers,
Will.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 9 13:00:38 2007