[01:02] <fullermd> darren: If that's the case, it's definitely a bug...
[01:03] <darren> is anyone here a developer on it? :)
[01:04] <fullermd> Probably someone who'll read the backlog if nothing else.  But if you could file a bug on it, that would be good.
[01:05] <fullermd> If not, I can try to bang one up later.
[01:14] <darren> no problem, I will :)
[03:55] <lifeless> mgz: I've merged most of your stuff - thanks. The subst stuff I was still not happy with so I reverted that, and I tweaked smoe other minor bits, In particular the setup test I made os specific via MatchesAny - trivial to do ;)
[07:57] <sobersabre> hi.
[07:57] <sobersabre> Is there something like svn:keywords in bzr ?
[07:58] <sobersabre> I want to embed revision number into the message  (something to signify revision numbe from the already build application)
[07:59] <bob2> not in bzr
[08:00] <bob2> I don't think any modern vc includes support for that
[08:07] <sobersabre> bob2: why is it a bad idea to have such a feature ?
[08:09] <bob2> hard to define what it should do, means more work for every file modification, then general feature mostly useless when you have atomic commits and easily accessible logs
[08:09] <bob2> if you just want to include a revno in something, add that to your build process
[08:43] <lifeless> sobersabre: bzr-keywords plugin
[08:43] <lifeless> bob2: $
[11:07] <rjek> Of course, adding interogation of bzr to your build process suddendly breaks everything when you make a release via bzr export.
[16:22] <ciss> hi!
[16:23] <ciss> does bazaar support a feature similar to place holders in subversion - that is, variables that are replaced in-code on a commit?
[16:26] <ciss> found a plugin: "Bazaar Keyword Templating Plugin"
[16:27] <jelmer_> hi ciss
[16:27] <jelmer_> yep, that's the plugin for that
[16:28] <ciss> jelmer_: i forgot to add the "never mind, found ..." to my last comment :)
[18:19] <lifeless> mgz: hi; so yes some care will be needed
[18:19] <mgz> lifeless: I'm just filing a bug.
[18:21] <mgz> bug 694800 is what still needs addressing on trunk testrepository
[18:21] <lifeless> thank you
[18:22] <mgz> I need to do a little cooking now, but am around-ish for the next hour at least.
[18:36] <lifeless> mgz: please try rev 133
[18:41] <mgz> that works for backslashes, but I don't see why you need to be so baroque about it.
[18:42] <mgz> spaces or other shell significant characters in the path will still be a problem due to the general design on composing bits of shell script.
[18:44] <lifeless> wll
[18:44] <lifeless> where we know its a path, we should indeed pass path element lists around
[18:45] <lifeless> as I said to you when you first looked at it, I'm not attached to the implementation, nor the api
[18:46] <lifeless> however I do have some clear goals, and I think the current code is closer to them
[18:46] <lifeless> and easier to expand into the right thing
[19:43] <mgz> lifeless: teeny note, the 'list' is just because it's my mailinglist email account, and doesn't need preserving in NEWS
[19:45] <lifeless> mgz: what nom de code would you like?
[19:47] <mgz> as per bzr whoami or "Martin [gz]" as disambiguation seems to work okay.
[19:48] <lifeless> ok
[19:49] <mgz> thanks!
[19:50] <lifeless> which would you prefer
[19:51] <lifeless> I don't generally put email addresses in NEWS, simply because of spammers and folks reaction to that
[19:51] <lifeless> so I'm inclined to do 'Martin [gz]'
[19:51] <lifeless> if thats ok
[19:53] <mgz> I think that's what I've been using recently, I'm not terribly consistent.
[20:59] <ovnicraft> hi guys, i ma trying to merge in my repo and get this error http://paste.pocoo.org/show/310507/
[20:59] <ovnicraft> i see the limbo dir and get N things what i cant understand
[21:01] <ovnicraft> how solve this and merge ok my repo?