Am 16.12.2011 19:53, schrieb Adam Walling:
When creating a new branch, obviously everyone will need to download
it for maintenance and etc.
No, only those that are actually using that branch and working on it
somehow need it.
The naive approach is to simply update and download the new branch
On Fri, Dec 16, 2011 at 12:53 PM, Adam Walling wrote:
>
> With 1.6, we would take advantage of being able to copy all of trunk to the
> new branch directory on the local filesystem, and then switch to the actual
> branch URL and update, therefore only transferring files that actually
> differ. Thi
On Fri, Dec 16, 2011 at 01:53:21PM -0500, Adam Walling wrote:
> When creating a new branch, obviously everyone will need to download it for
> maintenance and etc. The naive approach is to simply update and download
> the new branch from the server. However, with a large branch and with many
> users
When creating a new branch, obviously everyone will need to download it for
maintenance and etc. The naive approach is to simply update and download
the new branch from the server. However, with a large branch and with many
users simultaneously updating, this quickly overloads the bandwidth and may
