git-bzr-ng icon indicating copy to clipboard operation
git-bzr-ng copied to clipboard

Issue 12

Open putermancer opened this issue 13 years ago • 7 comments

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_REPO and then directly do git bzr push without 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.

putermancer avatar Dec 16 '10 17:12 putermancer

awesome, i'll take a look

termie avatar Dec 16 '10 17:12 termie

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

rbrito avatar Jan 04 '13 08:01 rbrito

@termie seriously did you really look at the patch? If you are not really working on git-bzr-ng just say it!

TimothyGu avatar Jun 03 '13 03:06 TimothyGu

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

@bloveridge @rbrito @TimothyGu

termie avatar Jun 03 '13 18:06 termie

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.

arvidjaar avatar Jun 03 '13 18:06 arvidjaar

Hi.

On Mon, Jun 3, 2013 at 3:34 PM, Andrey Borzenkov [email protected] wrote:

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.

For all intents and purposes, git's version of bzr allows me to clone repos that I couldn't with git-bzr-ng. It would be best if the best features of this project could be transplanted to git, so that we could have "one tool to rule them all".

Regards,

Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/ DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

rbrito avatar Jun 04 '13 00:06 rbrito

Agreed with @rbrito

TimothyGu avatar Jun 04 '13 00:06 TimothyGu