git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Gabriel Filion <lelutin@gmail.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: RFD: git-bzr: anyone interested?
Date: Mon, 26 Apr 2010 22:53:58 -0400	[thread overview]
Message-ID: <4BD651C6.5050501@gmail.com> (raw)
In-Reply-To: <p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com>

Hello,

On 2010-04-26 17:41, Chris Packham wrote:
> How far did git-bzr or git-remote-bzr get?
> 

I unfortunately haven't had much time to fiddle with this. Having a full
time job doesn't give me much space for experiences :( And on my free
time, I've been a bit busy with one of my projects..


I've tried simply "plugging in" the bzr-fastimport plugin to do the
communication part. They already implement output similar to what
git-fastimport expects. I was stuck on the part where you have to
specify "marks" files, and about where to place them, so I left it there
for now.

I'll try and work on this pretty soon, but since I'm doing this on spare
time, any help would be welcome. Maybe the good thing to do would be to
put up a page somewhere with a mini-roadmap and the info needed/the info
that was found out?
By using bzr fast-import, the whole thing shouldn't take too long.

> 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].

> [1] http://github.com/kfish/git-bzr/blob/master/README

This script needs you to install bazaar and the bzr "fast-import"
plugin. Normally the fast-export command is implemented by it. You need
a rather up-to-date version, though.
I've found this script to work mostly for pulling in changes from bzr
into git. Pushing has proven to be from slow to non-functional.


As for the interest in this: mine is in using only one tool to do the
work right and not having to switch from using 3 vcs tools (the current
situation at work is 2 -- git and svn -- but soon bzr will come in). And
for the one tool, I'd like to choose git.
stupid reason? probably. but I've tried bzr and I don't like it.

-- 
Gabriel Filion

  parent reply	other threads:[~2010-04-27  2:54 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
2010-04-27  0:58                   ` Chris Packham
2010-04-27  2:10                   ` Miles Bader
2010-04-27  2:53                 ` Gabriel Filion [this message]
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=4BD651C6.5050501@gmail.com \
    --to=lelutin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=judge.packham@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).