**** BEGIN LOGGING AT Sun Nov 18 02:59:59 2012 Nov 18 16:51:10 levonmaa: JaMa: Hi :) Nov 18 16:53:14 otavio: should I merge my first 2 patches then? Nov 18 17:01:46 JaMa: I think so; I think we all ought to be using our last code Nov 18 17:01:57 JaMa: so it makes easier to people to contribute Nov 18 17:02:23 JaMa: it will break, sure, but we're not promoting it as ready for use yet hehe Nov 18 17:03:09 ok Nov 18 17:04:00 JaMa: do you agree? Nov 18 17:04:49 already merged :) Nov 18 17:06:36 Personally I'd like to know the known issues so we can work on those as well Nov 18 17:07:45 ./2012-11-17.log:01:51 < JaMa> levonmaa: -qt-xcb was already added there, glxconvenience http://paste.debian.net/210017/ Nov 18 17:08:09 is known, I'll add beta1 to check what exactly changed in build (git log wasn't very helpfull in this) Nov 18 17:10:16 JaMa: the paste is not available Nov 18 17:10:33 JaMa: can you describe the issue more? Nov 18 17:12:19 ah sorry, it's build issue, xcb platform is using symbols from platformsupport/glxconvenience but not linking to them, so xcb linking fails Nov 18 17:12:34 Another question, why you named it 4.999? Nov 18 17:13:21 My initial idea was to package it as 5.0 (mostly as kernel) and ignore the 5.0.x or 5.0.0- Nov 18 17:13:31 and just bump PR and change as need Nov 18 17:13:45 otavio: repasted http://paste.debian.net/210469/ Nov 18 17:14:12 to be able to name 5.0.0 relase as 5.0.0 Nov 18 17:14:27 and upgrade from betaX or any git revision we're using now Nov 18 17:14:37 like kernel :) Nov 18 17:14:54 JaMa: and why not just call it 5.0 and ignore the bin versions? Nov 18 17:15:14 JaMa: for user, it doesn't matter much if it is 5.0.0 or 5.0.2 or so Nov 18 17:15:32 JaMa: and I see no ready why we'd not update it to 5.0. Nov 18 17:15:46 JaMa: so 5.0 would be the versioning after all Nov 18 17:16:05 JaMa: and when moving from beta2 to rc1 we'd bump PR Nov 18 17:16:37 well but then user don't see what he really gets Nov 18 17:17:32 who would expect beta2 in something named 5.0.0-r3 Nov 18 17:18:08 and correct naming allows us to work on different versions without issues (e.g. git and beta tarballs) Nov 18 17:21:07 JaMa: well ... I'd name it 5.0-r3 or so ... but I get your point Nov 18 17:21:49 and when PR is removed from oe-core we're all doomed :) Nov 18 17:22:54 JaMa: PR is not going to be removed but automated Nov 18 17:23:21 yes but then one build will have 5.0-r10 as beta1 and other 5.0-r1 as beta1 Nov 18 17:23:38 so better to be clear about version in PV not PR Nov 18 17:27:07 :-) Nov 18 18:16:48 JaMa: try git log --oneline --pretty --graph Nov 18 18:17:06 it also depends on which branch you're on Nov 18 18:18:57 actually, gitk --all might be the most helpful... Nov 18 18:30:07 nerdboy: for what? Nov 18 18:31:07 I meant just that I haven't noticed commit which should cause this between beta1 and beta2.. Nov 18 18:32:16 which is the point of the graphical view... Nov 18 18:32:47 plus i just learned about the --all switch Nov 18 18:33:28 seems like all the guis support it, at least gitk, gitg, and gitview all do Nov 19 01:22:49 it is possible that git will go down in the next few hours...the Colo location of our server is experiencing Heating Issues. Nov 19 02:28:04 I am going to shut down the Git/wiki server to protect things... **** ENDING LOGGING AT Mon Nov 19 02:59:59 2012