On Mon, Apr 26, 2010 at 7:53 PM, Gabriel Filion <lelutin@xxxxxxxxx> wrote: > 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.. Fair enough. My day job tends to suck up most of the time I want to spend in front of a computer too. > 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'm probably unqualified to help, not being familiar with bzr at all, but if you want a monkey to write test cases I can probably do that. >> [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. Actually I can probably contribute a snippet for your README file on how to install the required plugin if that would be helpful. It took me some fiddling an experimentation to work it out even after reading the bazzar documentation. > 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. My interest was purely around updating patches one project that we use that happens to use bazaar. Normally most things we do are either in git or built from tarballs + patches. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html