Re: Git to Bzr - what works?

[Eli Zaretskii]

> From: John Wiegley <address@hidden>
> Date: Wed, 15 Aug 2012 22:18:46 -0500
> 
> It's an inertia thing, really.  I could find a solution to my problem, I'm
> just not motivated to.  In fact, I'm anti-motivated each time I try to touch
> Bzr, and it's *just* weird enough from a Git standpoint to cause me problems.
> 
> Like when I commit, and the commit goes straight to remote (wait!  I wanted to
> push that with other commits!).  Or I set the up indirection, and find later
> that my push pushed to a local directory instead of remote (what?  you didn't
> get my change?  I just pushed it!).  Etc.

I think you will be much better off using Oscar's advice: using a
non-bound bzr branch where you can commit locally at will and push
upstream only when you decide to do so.  That should allow you a
workflow that is largely mechanic and does not require to rewire your
brain for bzr.