/srv/irclogs.ubuntu.com/2014/01/27/#bzr.txt

=== superfly is now known as superly
=== superly is now known as superfly
awilkinsProbably a common and stupid question but googling answer is hard12:19
awilkinsWhat's the equivalent of git rebase -i in bzr12:19
awilkinsWant to remove one revision from the history of a branch12:19
awilkinsHum, in other words : https://bugs.launchpad.net/bzr-rewrite/+bug/24315012:21
ubot5Ubuntu bug 243150 in bzr-rewrite "support -i flag as per git" [Wishlist,Triaged]12:22
awilkinsMay just reverse CP this revision12:22
jelmerawilkins: yeah, sounds like it13:12
awilkinsjelmer, Reverse cherry pick was more appropriate to this case anyway13:12
jelmerah, cool13:14
=== [emmajane] is now known as emmajane
=== emmajane is now known as ejfood
=== ejfood is now known as emmajane
=== jordan_ is now known as jordan
achiangwhen doing a bzr merge of a branch, is there a shortcut to have the commit message just say what branches i pulled from?21:28
achiangi'd settle for any type of shortcut/boilerplate for a merge commit message21:29
rozzinachiang: "bzr commit -m"?23:41
achiangrozzin: i still have to supply an arg for -m right?23:44
jelmerachiang: yep23:45
jelmerachiang: there is nothing like what you're asking for AFAIK23:46
achiangso that's not a shortcut at all23:46
jelmerit would not be hard to do a hook around 'bzr merge' that sets a proposed commit message23:46
achiangjelmer: darn, too bad. it's just a little papercut, but i find myself frustrated every time i trip over it23:47
jelmerachiang: I'm sure patches are welcome :)23:48
achiangjelmer: i think i'd rather just build up scar tissue ;)23:48
jelmerheh23:53

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