[01:39] I have a local bzr branch that has a number of files and directories in it. I would like to export a single file (which has been renamed, if it matters) with the history of just that file into a new bzr repository. Is that possible/how do I do it? [02:17] split, I guess [02:17] or bzr-rewrite [02:17] (or not bother, and just put the file in a new repo) [02:19] split is just a shortcut to rm'ing everything else and committing. [02:19] You can't move just one file's history, because there isn't any such thing. Files don't have history; history has files. [02:19] With something like rewrite, you could in concept create a new history with just that one file in it that looks a lot like the existing one; whether the tool makes that practical, I have no idea. [02:37] OK, put it differently, can I rewrite the history to remove everything else? [02:37] Keeping the history is important because bzr blame has saved my behind more than once already. [03:22] Yeah, that's what you'd have to do; create a new history that looks pretty much like the existing history of the file. [03:23] Sorta a (foreach `bzr log $FILE`; set contents ; commit with same log/committer/date) process. [03:23] Which is conceptually in rewrite's domain. Whether such a thing is actually implemented there, I don't know. [17:56] hi... it seems that there's a bug in bzr log [17:57] I merged stable branch into trunk, and the tag on the last revision in stable branch is not shown in bzr log -r -n0 [17:57] however when I want to add it in Bazaar Explorer, it says that the tag already exists and asks me if I want to move it [17:58] * I run bzr log -r -n0 in trunk of course === herb is now known as herb__ === herb__ is now known as herb [18:06] oh no... I wasn't able to reproduce it on new branch :( [18:14] does anybody know what could cause this behaviour? === r0bby is now known as robbyoconnor