Re: Git to Bzr - what works?

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 15 Aug 2012 22:18:46 -0500 John Wiegley <johnw@newartisans.com> wrote: 

JW> The problem for me is, I have no other use for Bazaar, and my brain is too
JW> full to try and master another VCS to the extent of being fluent enough not to
JW> be bothered by things like this, so instead I just keep my changes local.

JW> It's an inertia thing, really.  I could find a solution to my problem, I'm
JW> just not motivated to.  In fact, I'm anti-motivated each time I try to touch
JW> Bzr, and it's *just* weird enough from a Git standpoint to cause me problems.

JW> Like when I commit, and the commit goes straight to remote (wait!  I wanted to
JW> push that with other commits!).  Or I set the up indirection, and find later
JW> that my push pushed to a local directory instead of remote (what?  you didn't
JW> get my change?  I just pushed it!).  Etc.

I have had similar experiences.  I would conservatively estimate it cost
me 40 man-hours to work with Bazaar instead of Git when I was doing the
GnuTLS integration.  I lost work several times!  Perhaps I'm an idiot
unable to grasp the subtleties of Bazaar, but I think the *cost* of
using Bazaar to casual contributors like me should be considered.

(asbestos underwear on, preparing underground bunker, etc.)

If a technical solution must be had (and I don't think that this is a
techical problem), let's do it at the origin, providing Git and Bazaar
repositories that synchronize.  Hire/find a person to do it.  Their time
will be spent developing synchronization tools and procedures so the
rest of us won't have to.  Let's not push that pain out to the
contributors in the form of plugins and walkthroughs.

Sincerely
Ted