[02:33] <LeoNerd> marioxcc: No. I usually do that by creating new sibling directories with  .BRANCHNAME  suffixed on their names
[02:34] <LeoNerd> You can easily create one with e.g.  bzr push ../This-Thing.BRANCH
[02:34] <marioxcc> LeoNerd: Ok.
[02:34] <marioxcc> LeoNerd: In the time before you reply I found a “bzr-col” for “co-located” branches. This seems to be what I want, except that it seems to be dead (last release is from 2012 I think).
[02:35] <marioxcc> Are you aware of something like it?
[02:35] <LeoNerd> Nope. Though I don't really use anything like that
[02:35] <LeoNerd> I prefer to have different working trees, because I tend to have lots of derived tempories (i,e. compiled code and the like), so I like to keep them in different places too
[02:47] <marioxcc> LeoNerd: Ok, thanks.
[11:07] <Walex> marioxcc: LeoNerd: checkouts can approximate that, as in http://doc.bazaar.canonical.com/bzr.2.7/en/user-reference/checkouts-help.html
[11:08] <Walex> there is: "Another possible use for a checkout is to use it with a treeless repository containing your branches, where you maintain only one working tree by switching the master branch that the checkout points to when you want to work on a different branch."
[23:59] <jelmer> LeoNerd: colocated branches in the git/mercurial style are supported by default in bzr >= 2.5, but the syntax for addressing them is still a bit annoying ("file://blah,branch=foo")