[02:28] I'd like to get the last date of revision in my current working copy to be used in a Makefile. What is the recommended way to do that? [02:33] Look at version-info [02:51] fullermd: Is that a bzr command? [02:53] fullermd: It's pretty slow to run. Thanks though. I'll look into it. [21:04] How do I get the logs for a file that is no longer visible? bzr log password.c [21:04] gives me : bzr: ERROR: Path unknown at end or start of revision range: libmysql/password.c [21:04] hi nealmcb [21:04] have you tried specifying a revision in which the file still exists ? [21:04] jelmer: Howdy! [21:05] well the first issue is figuring out when that would be [21:07] jelmer: And I did try bzr log -r tag:mysql-4.0.1 password.c which should have it, but got no result [21:08] nealmcb: shouldn't that be bzr log -r tag:mysql-4.0.1 libmysql/password.c ? [21:08] well, I'm in that directory now, thought that was enough [21:08] yeah, it should be === tomaw_ is now known as tomaw [21:09] * jelmer tries to remember how the per file log logic works [21:12] I also tried looking at a revision and later: bzr log -r tag:mysql-4.0.1.. password.c [21:12] and got bzr: ERROR: Start revision not found in left-hand history of end revision [21:13] jelmer: but this helps find where it still existed: bzr ls -r tag:mysql-4.0.1 [21:15] ....if I do that for previous revisions with boolean search.... [21:17] nealmcb: alternatively, it should be possible to just do "bzr log -v | less" and search for libmysql/password.c [21:20] jelmer: useful trick - I thought about that before with just a grep, but then I wouldn't necessarily get all the context I wanted, which could be very big... [21:20] it's also pretty slow to go thru the whole log.... [21:21] Yeah; we should improve log to do the right thing. [21:21] It's not entirely trivial as there may have been multiple different files that have had that particular name over the course of history [21:23] odd - the first hit was on revno 2 - so no log of the deletion?? [21:23] nealmcb: there should be [21:24] nealmcb: perhaps its parent directory was renamed at some point before it was deleted? [21:25] Ahh - https://bugs.launchpad.net/bzr/+bug/181520 [21:25] Ubuntu bug 181520 in Bazaar "bzr log FILE don't show revisions where file was removed" [High,Confirmed] [21:25] 3 years old.... [21:26] Got any handy scripts to do binary search on the "ls" command? I can't think of anything better right now.... [21:26] nealmcb: you're not using "bzr log FILE" now though are you? [21:27] jelmer: Nope - bzr log -v |less [21:27] another thing you might try is "bzr log -r2.. libmysql/password.c" [21:28] using Bazaar (bzr) 2.2.4 [21:28] I get bzr: ERROR: Path unknown at end or start of revision range: libmysql/libmysql/password.c [21:29] Oh - removing libmysql/ since I'm in the directory -- and I get nothing [21:30] (no error message, no log beyond what I see in revno 2) [21:31] this is in a standard mysql tree? [21:31] oops - I had switched to look in a branch of an old revision.... now I'm getting logs [21:34] jelmer: Ahh - good - this even shows me the removal: bzr log -v -r2.. password.c [21:34] when I use the right tree.... [21:34] but it sure would be nice to be able to find out the last time the file was removed. [21:34] jelmer: thanks! [21:38] nealmcb: np [21:38] nealmcb: It would indeed be nice to have some way to refer to removed files, not just to files in the start or end tree. [21:41] bzr search can do some of that FWIW [21:42] ah, that's good to know [21:43] lifeless: No help could be found for 'search' [21:44] nealmcb: it's a separate plugin - lp:bzr-search [21:47] lifeless: after install, bzr help search refers to a mysterious "QUERY" argument - where does one find more? [22:04] nealmcb: run bzr index [22:04] nealmcb: then bzr search libmysql/libmysql/password.c [22:06] hmm, I may not have wired it up; it certainly knows the path [22:06] nealmcb: I was mainly mentioning it to jelmer, in case he is looking at ways to address finding deleted files in core [22:16] lifeless: Re: 'This locates documents in bzr at a given url and creates a search index for that url' [22:17] I'm still puzzled - are documents just any sort of file? url would typically be a local path (needs to be a file:// url or not?) [22:17] is it a full-text index? of all previous revisions? If it is too big is there a way to delete the index? [22:18] its a full text index [22:18] paths, deltas to files etc [22:18] its stored in .bzr/bzr-search [22:18] you can just rm that dir [22:19] by url it means any location you can pass to bzr for e.g. info/log etc [22:20] can I just index a directory? I try bzr index . and it says that isn't a branch. [22:20] would it return a hit for every revision, or summarize them somehow? [22:20] (sorry to pester you with questions....) [22:23] nealmcb: you can only index a branch, though indexing a subdir of a branch is an interesting question its not been implemented [22:23] bzr index $(bzr root) [22:23] will find the root of your branch for you [22:25] I just did [22:25] bzr search socket timeout [22:25] in bzr [22:25] http://pastebin.com/NtsULbNn [22:25] is the output [22:25] its a little geekish [22:26] the revisions can be passed to other commands like log though - via '-r revid:$therevision' [22:26] or show in annotate with --show-ids, that sort of thing [22:40] lifeless: Thanks for the tips, and the code! [22:42] my pleasure [22:42] if you wanted to file a bug on including/excluding paths to index, that would be cool. [22:43] * lifeless afks