On Wed, Jul 19, 2006 at 01:45:27PM -0000, Pavel Šimerda wrote:
> "where the working tree cannot be created"
>
> Why can't you create and update working tree using push (I mean with an
> option like --force-tree)? It would allow you to use bzr e.g. on
> webhosting services.
The arguments I recall (please speak up if there are more) are
basically:
- it's hard to detect changes in the remote workingtree and do the
right merging magic.
- pushing the workingtree is a lot of duplicate data.
For the webhosting use case, having an option to just throw away the
workingtree and push everything again might be satisfactory. Shouldn't
be too hard to write a plugin for.
On Wed, Jul 19, 2006 at 01:45:27PM -0000, Pavel Šimerda wrote:
> "where the working tree cannot be created"
>
> Why can't you create and update working tree using push (I mean with an
> option like --force-tree)? It would allow you to use bzr e.g. on
> webhosting services.
The arguments I recall (please speak up if there are more) are
basically:
- it's hard to detect changes in the remote workingtree and do the
right merging magic.
- pushing the workingtree is a lot of duplicate data.
For the webhosting use case, having an option to just throw away the
workingtree and push everything again might be satisfactory. Shouldn't
be too hard to write a plugin for.
Wouter van Heyst