[08:48] <gour> morning
[08:48] <gour> my problem from yesterday was due to old version of dulwich - i did brz lp:dulwich not being aware that new version lives in git repo elsewhere
[09:02] <gour> is there any gui working atm with brz?
[09:08] <gour> bzr-git serves those who want to "use Bazaar as their VCS client on projects still using Git as their VCS tool", but I wonder about vice versa, iow. what about those who want to primarily use Bazaar as their VCS and occasionally export their repo to git(hub)?
[09:09] <gour> what is trade-off in using git format for branches in comparison with brz's native 2a format?
[09:10]  * gour just created shared repo
[10:24] <jelmer> gour: converting back and forth between the different formats regularly is going to be slow
[10:24] <jelmer> I'd recommend just using the git format if you're going have to eventually push to github
[10:25] <jelmer> That way you can also easily fall back to just using git while bree
[10:25] <jelmer> breezy is pre-beta
[10:39] <jelmer> s/breezy/brz-git/
[11:20] <gour> jelmer: and what if i'd mostly work in brz and just want from time to time export (theme for static site generator) new release to the git format so it can be linked by the upstream project?
[11:23] <jelmer> gour: why do you want to use the bzr format locally?
[11:24] <gour> jelmer: i assume that 'native is better' ?
[11:24] <jelmer> gour: with the new brz-git, both formats are equally native (though the git format is obviously less well tested)
[11:25] <gour> jelmer: ok, what about git formats and shared repo, that does not work together and one has to use branch per repo with git?
[11:26] <jelmer> gour: git formats don't support shared repositories
[11:26] <gour> ok, as i thought :-)
[11:26] <jelmer> you can use git-style multiple branches per repository (colocated branches)
[11:28] <gour> via plugin?
[11:34] <jelmer> no, natively
[11:34] <jelmer> admittedly colocated branches are still in a rough state too
[11:36] <gour> ohh, didn't know that was merged into the core
[11:38] <gour> now found it as 'development-colo' format
[11:39] <jelmer> gour: you don't need development-colo, it works with the default format
[11:47] <gour> jelmer: where can i read about that?
[11:48] <jelmer> gour: I don't think we've documented it anywhere yet, it's not in a state yet where I'd recommend using it
[11:51] <gour> jelmer: does it resemble http://doc.bazaar.canonical.com/plugins/en/colo-plugin.html ?
[11:58] <jelmer> gour: no, it's unrelated to that
[12:11] <jelmer> You can see some of it in action when running brz in an existing git repo
[12:12] <jelmer> E.g. 'brz branches' will list all branches
[12:12] <jelmer> And 'brz switch' allows switching between them
[12:15] <gour> just cloned some repo from the github to compare sizes and 'du' shows the same size
[12:15] <gour> that's cool
[12:16] <gour> is there any workable gui for brz which can be recommended for not-so-savvy users?
[12:23] <fullermd> I've gotten along reasonably well using bzr for a project and git-bzr-ng to schlep up a mirror on github.
[12:27] <gour> fullermd: that's nice to hear...my current VCS for private stuff is Fossil, but I anticipate that brz will become my favorite one enabling me to inter-operate with git(hub) projects
[12:30] <gour> what is the use of cheap branching in git when working with branches, especially with remote ones, is so convoluted...
[12:40] <jelmer> gour: there's no functioning UI at the moment
[12:40] <jelmer> there's lp:qbrz, but it hasn't been updated for the latest round of API changes in Breezy
[13:02] <LeoNerd> Has bzr-rewrite disappeared from debian?
[13:03] <jelmer> LeoNerd: yes
[13:03] <LeoNerd> Hmm.. Isee
[16:09] <gour> does extmerge work with brz?
[18:08] <jelmer> gour: none of the existing bzr plugins work with breezy, though some (like extmerge) are probably easy to port
[20:35] <gour> jelmer: thanks