Issue 12 #13
Issue 12 #13
Conversation
…h older-style repos (ie pack-0.92) on newer versions of bzr that default to something else (ie 2a)
|
awesome, i'll take a look |
|
@termie, did you have a time already to look at the pending pull requests? For instance, this comment of yours is 2 years old now... |
|
@termie seriously did you really look at the patch? If you are not really working on git-bzr-ng just say it! |
|
i haven't spent much time looking at these pull requests, no, i was working on fixing an old bug and eventually got demotivated by having to continue to work with bzr (i wrote this thing because i hate bzr), i am okay giving somebody else access to the repo if they want to go through a bit and merge comment on things, and can look into transferring maintainerness if somebody is interested |
|
Current GIT includes bzr remote helper which allows to use native git interface (git pull/git push) with bzr repo. It has its share of issues, of course. May be it makes sense to try to improve it. |
|
Hi. On Mon, Jun 3, 2013 at 3:34 PM, Andrey Borzenkov
For all intents and purposes, git's version of bzr allows me to clone Regards, Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA |
|
Agreed with @rbrito |
This patch addresses issue 12 described here: https://github.com/termie/git-bzr-ng/issues/#issue/12
There may be a better way of doing this. For example, storing it along with the other config options and passing it along to init_repo based on the desired branch, a la:
[bzr "master"]
bzr = bzr/master
format = pack-0.92
However, this did not look trivial, as init_repo seems to be frequently called without reference to a specific branch just to make sure directories are created. It could be that I missed something.
With this patch, you can do
git bzr clone --format=pack-0.92 PATH_TO_BZR_REPOand then directly dogit bzr pushwithout specifying the format again -- though the push, sync, etc commands do also take a --format option if one desires to pass it for when init_repo is called to make sure the directory exists. I assume that the directory should only NOT exist if the user has done something weird / manual, thus being able to specify it manually for the other calls seemed to make sense.