Recommended use of Bazaar for single-committer multiple-machine projects?

[Viktor Nagy]

I have never used shelve/unshelve, but couldn't you work around
--local with it and then simply update your branches?

Anyway, even though my settings is seemingly much simpler, I use the following:
* have one central repo that I can access anytime
* have its mirror with working tree on my laptops
* push every time when I leave without a laptop
* pull every time when I have to work on a different laptop/PC

As I am the only one updating the central repo merging is not
necessary as long as I follow the above steps. --local is not needed
either as I use branches not just checkouts.

V

2008/12/12 Matthew D. Fuller <fullermd at over-yonder.net>:
> On Fri, Dec 12, 2008 at 06:31:27PM +1100 I heard the voice of
> Mary Gardiner, and lo! it spake thus:
>>
>> OK. so essentially you don't in this model do a lot (or any) --local
>> commits. It may be that this is an improvement in terms of avoiding
>> the various two-merges problems that working directly in the
>> checkout cause.  I'll give it a go. (Still interested in other
>> workflows though.)
>
> That's the sort of thing I'd aim at too.
>
> I consider --local to be far more of an escape hatch, and far less a
> daily tool.  It's an inherently schizophrenic thing to do; branches
> can be shared (as in a checkout) or independent; --local users the
> former to emulate the latter.  Certainly it has unnecessary bugs like
> you've mentioned, but even with them fixed, it's [IMAO] much better
> considered a special-case stopgap, than a regular-use device.
>
>
> --
> Matthew Fuller     (MF4839)   |  fullermd at over-yonder.net
> Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
>           On the Internet, nobody can hear you scream.
>
>



-- 
Viktor Nagy - http://viktornagy.com
PhD student
Toulouse School of Economics