Re: RFD: git-bzr: anyone interested?

From: Conrad Parker <conrad@metadecks.org>
Date: Aug 6, 2010, 07:19 UTC
Message-ID: <AANLkTi=a27OtQX-oNwPqmXDUmZHFyKo+fPZCRgSv04G3@mail.gmail.com>
In-Reply-To: <p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com>

Hi,

Anyone interested in git-bzr might also want to look at some recent rewrites; from the current git-bzr README:

The following are rewrites in Python and may offer better bzr integration:
  * http://github.com/termie/git-bzr-ng
  * http://github.com/matthew-brett/git-bzr

(... and I'd also be interested to know how well either of these work :)

cheers,

Conrad (kfish).

On 27 April 2010 06:41, Chris Packham <judge.packham@gmail.com> wrote:

Show 31 quoted lines

> Hi,
>
> How far did git-bzr or git-remote-bzr get?
>
> I've tried git-bzr from the repo and I seem to be stumbling on bzr not
> having the fast-export command after I install the fast-import plugin
> as per [1]. So I think its a bazzar problem not a git-bzr one. Has
> anyone got a fully worked example including the installation of the
> required bits and pieces.
>
> Alternatively what I'm really trying to do is update a series of
> patches for an upstream project that is managed with bazzar. We have
> 30 or so patches with our customizations so I'd like to get git (or
> bzr) to do the heavy lifting for me. In git I'd do something like this
>
> git clone <upstream>
> git checkout <tag that corresponds to the version of the tarball we use>
> git checkout -b our-patches
> git am <patches>
> git rebase <tag that corresponds to the new version we want to use>
> git format-patch ...
>
> Anybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)
>
> [1] http://github.com/kfish/git-bzr/blob/master/README
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>