bzr-gtk vs. QBzr

[Alexander Belchenko]

Russel Winder пишет:
> John,
> 
> On Thu, 2009-02-26 at 08:32 -0600, John Arbash Meinel wrote:
> 
>> If you are doing 'commit --local', then it isn't a mirror. It sounds
>> more like you need to be clearer about what branches are a *mirror*
>> (identical to remote) and what branches are a local working copy.
> 
> I agree.  The problem comes though when one wants to update the mainline
> but one is having lunch in the Banana Leaf Canteen rather than at home
> connected to the Internet.  (Whilst there are a number of 802.11 access
> points visible in the Banana Leaf Canteen, they are all either private
> with at least some protection, or part of The Cloud or BT OpenZone
> networks.  These operators charge hugely extortionate, and unacceptably
> large amounts of money for Internet access.  No account, no access.)
> 
> OK I agree that the scenarios is now getting muddled.
> 
> What it does raise though is the hoary chestnut (as opposed hoary
> hedgehog :-) of Bazaar garbage collection.  With Git you create a
> feature branch, do a merge, delete a feature branch, do a garbage
> collect and you can be fairly certain that any extraneous material is
> excised from the repository.  With Bazaar, if I create a feature branch
> in a shared repository I am not certain there is a way of deleting that
> branch and there being any certainty that the shared repository will not
> contain excess material.  Or maybe I am wrong.  Anyway this leads me to
> the possible fallacious feeling that branches is shared repositories
> need to be long lasting ones, and that the only garbage free way of
> having feature branches is to have them be self-standing branches
> outside of a shared repository.  For a small branch this is fine, for a
> big branch it probably isn't.

I don't understand your concern about garbage collecting. If you're 
merge your feature branch to mainline all revisions will go there.
If you do uncommit in the branch inside shared repo the garbage will
stay there anyway. It seems like only stacked branching for feature
branches is real answer today.