[07:27] morning [07:29] we're considering to adopt bzr instead of hg, but like bitbucket's free repos (although we don't need much space) and considering that, afaik, bzr-git is more mature than bzr-hg, we wonder what would we miss of bzr's metadata if using bzr-bzr-git @bitbucket? === yofel_ is now known as yofel [10:32] gour: hi [10:32] jelmer: hiya [10:32] gour: bzr-git pushing into git is still experimental fwiw, there are some known corner case bugs [10:33] gour: you'd miss text revision information (used during merge), support for ghosts (data referenced but missing), multiple author support, support for revision properties (--fixes, etc) [10:34] jelmer: hmm...this is expensive [10:35] i think about adopting bzr considering it's even simpler/safer for potential contributors than hg (we don't consider git)...another option might be fossil... [10:36] jelmer: any estimation when bzr-git might be good-enough (if nto already) for collaboration with git projects? [10:39] i also wonder how does bzr-git compare with hg-git? does it offer better collaboration tool with git projects? [10:41] gour: I'm not sure; nobody is actively fixing those issues in bzr-git at the moment. [10:41] jelmer: you're the only developer? [10:42] gour: These days I'm just using git itself for projects that I work on that are in git. [10:44] jelmer: ahh, i see...i consider life is too short to think about git :-) [10:44] gour: I'm not sure how it compares to hg-git; the way in which hg-git hooks into mercurial seems a lot more hackish, but it might work a lot better in practice. [10:45] bzr-git's support for importing from git repositories works really well btw, it's mostly pushing from bzr into git for which there are some known issues [10:48] what is the future of bzr-hg then? even less bright? [10:50] ..in any case, it seems it's better to stick (if we decide so) to use bzr & LP despite LP's lack pf private repos and use hg/bitbucket when we need it...LP's bugtracker is, imho, much better than bb/github [10:51] pipeline is bzr's 'equivalent' for hg's MQ? [10:56] gour: I'm doing occasional bug fixing to bzr-git; I haven't used or contributed to bzr-hg in a long time, also because none of the projects I'm involved in use it anymore. === jelmer changed the topic of #bzr to: Bazaar version control | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ [10:57] gour: bzr-pipeline and bzr-loom are equivalents to MQ I think (have never used MQ) [10:58] jelmer: ok. thank you [10:59] i believe bzr-git & bzr-hg could be useful in general as a mean to stay with bzr & work with git & hg projects isntead of always switching between different VCS-es [11:00] otoh, it's shocking to see that github is populated with so many projects... [11:00] gour: sure, I agree that's why they're useful as well; and one of the reasons I work on bzr-git [11:00] gour: there's just 24 hours in a day though ;) [11:01] jelmer: you're not workin for canonical? [11:04] gour: I am, but most of my contributions to bzr-git and bzr-hg I did before I joined [11:05] jelmer: well, i like to hear that...it means there is future for bzr ;) [11:05] congrats; btw ;) [18:00] I accidentally pushed my branch to a wrong location (that is, suppose it should be pushed to A, but I pushed it to B). Is there anyway to remove the change from B? [18:25] evillyEvil: bzr uncommit B [18:26] lifeless: That will revert the latest changes in B? [18:27] What if I've added multiple revisions before accidentally pushing the branch to B? How do I specifically say what revisions I want uncommit? [18:28] you can pass -r -2, for instance [18:28] or just run it multiple times [18:39] I see. Thanks for the tip [19:45] i'm looking to return back from hg to bzr and wonder whether looms or pipeline is closer to hg's MQ? [19:48] pipeline [19:48] loom versions the queue, and its evolution, which is substantial added complexity, something MQ doesn't do. [19:53] thanks...let me read about it