[00:51] <Noldorin> can bzr edit past commit messages?
[00:56] <Noldorin> i remember this being discussed some time ago, but haven't heard much about it recently.
[01:00] <maxb> Not really
[01:00] <maxb> Only by uncommit/commit, so only for the top commit in history, without pain
[01:00] <Noldorin> maxb, that's what i thought yeah
[01:00] <Noldorin> is it under consideration for the future?
[01:01] <Noldorin> some ideas on how to do it were discussed on the mailign list some time ago i think
[10:36] <maxb> err..
[10:37] <maxb> since when did "bzr ci" in a debian package commit without prompted for a log message?!
[10:42] <lifeless> sounds like a bug
[10:42] <lifeless> the commit template facility is meant to generate a default, not an actual
[16:16] <jimis> hello, can you point me to some documentation for using bzr like git? That is with full branch downloaded in a directory, and switching between local feature-branches in that same directory?
[16:18] <jimis> the reason is that when you have huge repositories, it's often prohibitive to keep 10-20 branches in separate directories
[18:23] <LarstiQ> jimis: bzr-colo
[18:30] <jimis> LarstiQ: I was aware of that but somebody had told me that it is possible without plugins
[18:31] <jimis> Plus it would be nice if I could find some section in the documentation about that workflow, bzr-colo isn't much documented
[18:35] <LarstiQ> jimis: depending on what that person meant, yes
[18:36] <LarstiQ> jimis: you still need to have separate directories around for your branches, but they can be without working trees
[18:36] <LarstiQ> jimis: and then you just use the regular `bzr switch` between them
[18:38] <LarstiQ> jimis: if that is enough for you, then good :) But it's not the "full" git workflow from a purist standpoint.
[18:39] <jimis> LarstiQ: how can I have multiple dirs, but not consuming multiple-times the disk space?
[18:40] <LarstiQ> jimis: for example, `bzr init-repo --no-trees ~/src/project; cd ~/src/project; bzr branch somewhere-trunk; bzr branch trunk feature1; bzr co --lightweight feature1 work;`
[18:41] <LarstiQ> jimis: only the 'work' dir will have a working tree
[18:41] <LarstiQ> jimis: the key thing there is --no-trees
[18:41] <LarstiQ> jimis: if you already have a repository you can use `bzr reconfigure` to toggle that on or off
[18:50] <jimis> LarstiQ: thanks, that is good enough
[18:50] <jimis> I'll try it and if it works well I'll make a request to document that workflow in bzr's user guide