From: Dmitrijs Ledkovs <dmitrij.ledkov@ubuntu.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: Gabriel Filion <lelutin@gmail.com>, git@vger.kernel.org
Subject: Re: RFD: git-bzr: anyone interested?
Date: Tue, 27 Apr 2010 00:46:50 +0100 [thread overview]
Message-ID: <m2u86ecb3c71004261646zd17cafdcy85cd2ce522a771d5@mail.gmail.com> (raw)
In-Reply-To: <p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com>
On 26 April 2010 22:41, Chris Packham <judge.packham@gmail.com> wrote:
> Hi,
>
> How far did git-bzr or git-remote-bzr get?
>
Don't know, never used.
As far as I know bzr-git can fetch, clone, commit and push to/from
bzr/git repos. Not sure why you would want git-bzr
> 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.
>
fast-export would loose information AFAIK use bzr-git with dalwich.
> 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>
bzr branch <upstream>
> git checkout <tag that corresponds to the version of the tarball we use>
bzr checkout -rtag:<tagname> tag-branch
> git checkout -b our-patches
cd tag-branch
> git am <patches>
bzr patch patch1 patch2 patch2
> git rebase <tag that corresponds to the new version we want to use>
bzr rebase ../<upstream>
> git format-patch ...
>
bzr log -p; or bazaar send -p or create bundle depends on what you want.
> Anybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)
>
Although I think you really want
http://wiki.bazaar.canonical.com/BzrPipeline which helps you import
patches ontop of a branch, update upstream, update (merge) patches,
and export them again. It's something like quilt, topgit but
bzr-styled ;-)
> [1] http://github.com/kfish/git-bzr/blob/master/README
=) hope this helps.
ps. anyone can help with repo.or.cz not reusing objects from parent
when pushing to a fork? reported to admin@repo.or.cz they can
reproduce the bug but something dodgy is going on. Thanks. Me will
shut up about bzr now =)
next prev parent reply other threads:[~2010-04-26 23:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 18:13 RFD: git-bzr: anyone interested? Gabriel Filion
2010-02-18 18:37 ` Sverre Rabbelier
2010-02-19 7:05 ` Gabriel Filion
2010-02-19 7:49 ` Sverre Rabbelier
2010-02-19 12:52 ` Gabriel
2010-02-19 13:38 ` Sverre Rabbelier
2010-02-19 15:15 ` Writing git remote helpers Gabriel
2010-02-22 4:53 ` RFD: git-bzr: anyone interested? Gabriel Filion
2010-02-19 13:55 ` Ilari Liusvaara
2010-02-22 4:42 ` Gabriel Filion
2010-02-22 10:51 ` Ilari Liusvaara
2010-02-23 3:20 ` Gabriel Filion
2010-02-23 12:45 ` Ilari Liusvaara
2010-04-26 21:41 ` Chris Packham
2010-04-26 23:46 ` Dmitrijs Ledkovs [this message]
2010-04-27 0:58 ` Chris Packham
2010-04-27 2:10 ` Miles Bader
2010-04-27 2:53 ` Gabriel Filion
2010-04-27 8:47 ` Dmitrijs Ledkovs
2010-04-27 17:00 ` Chris Packham
2010-04-27 17:13 ` Chris Packham
2010-04-27 23:22 ` Dmitrijs Ledkovs
2010-08-06 7:19 ` Conrad Parker
2010-08-07 3:36 ` Miles Bader
2010-08-07 8:48 ` Gabriel Filion
2010-08-07 13:37 ` Miles Bader
2010-08-07 13:03 ` git-archimport (was: Re: RFD: git-bzr: anyone interested?) Jakub Narebski
2010-08-07 13:11 ` git-archimport Matthieu Moy
2010-02-20 13:58 ` RFD: git-bzr: anyone interested? Felipe Contreras
2010-02-22 2:43 ` Gabriel Filion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2u86ecb3c71004261646zd17cafdcy85cd2ce522a771d5@mail.gmail.com \
--to=dmitrij.ledkov@ubuntu.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=lelutin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).