/srv/irclogs.ubuntu.com/2013/07/10/#bzr.txt

=== FourDoll1rs is now known as FourDollars
=== jpds is now known as Guest46086
=== quicksil1er is now known as quicksilver
=== milleja46_ is now known as milleja46
=== vednis is now known as Guest75277
=== yofel_ is now known as Guest48668
=== Guest48668 is now known as yofel
=== thomi_ is now known as thomi
pmatulissay i do a 'bzr branch lp:whatever'; then 'bzr merge lp:~jdoe/whatever/review1'; and then jdoe does more work before i merge his work into trunk (the 'whatever' project).  how do i avoid having to include a commit for the original merge?  i'd rather just have a single commit19:56
=== vednis is now known as Guest31918
=== yofel is now known as Guest395
=== DarrenS is now known as Guest18637
=== Guest395 is now known as yofel
eriduis there a way to tell git-import to use the development-subtree repo format? I want to import a repo with submodules.20:22
jelmereridu: nested trees aren't really supported yet - bzr-git supports them, but bzr itself does not20:25
eridujelmer: I'm aware of this and assume all risks related to using nested trees -- I understand they will blow up in my face, shoot my dog, and when I least expect it, destroy all that I love and hold dear20:26
jelmeryou can sort of force the combination to work by initializing the target repo before running git-import20:26
jelmerbzr init-repo --development-subtree foo20:26
eriducan you git-import over an existing repo?20:26
jelmerbzr git-import /url/for/git-repo foo20:27
jelmereridu: yes20:27
eridujelmer: thanks! didn't know that20:27
fullermdThe trick is to constantly expect your dog to be shot.  Then you're safe.20:28
=== iBasic is now known as BasicOSX
eriduhah, that made bazaar crash20:35
eriduI expected my dog to be shot, but not that quickly20:35
=== wedgwood is now known as Guest90326
=== Guest90326 is now known as wedgwood
=== verterok` is now known as verterok
=== elmo_ is now known as elmo

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!