groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux-devel
groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux-devel
groovy3shoes has joined #crux-devel
groovy2shoes has quit [Ping timeout: 240 seconds]
XXX1232 has quit [Ping timeout: 250 seconds]
farkuhar has joined #crux-devel
XXX1232 has joined #crux-devel
Guest3955 has joined #crux-devel
Guest3955 has quit [Client Quit]
farkuhar has quit [Ping timeout: 256 seconds]
SiFuh_ has joined #crux-devel
SiFuh has quit [Ping timeout: 250 seconds]
groovy3shoes has quit [Remote host closed the connection]
groovy3shoes has joined #crux-devel
groovy3shoes is now known as groovy2shoes
farkuhar has joined #crux-devel
<beerman>
farkuhar: quick question, whats the latest crux release?
<farkuhar>
beerman: I think I see your point. The git workflow is still rather mysterious to me, so I might have some erroneous assumptions about how multiple heads and branches are managed.
<beerman>
right, well then
<beerman>
just to add some more confusion to it, all my changes i did in a local branch, that was merged into the public 3.7 that jue created around 7th of january or something ;) so all commits you see I did before that point werent even public. funny eh?
<farkuhar>
very confusing, i agree.
<beerman>
Not so confusing, really..
<beerman>
its all in the git log
<beerman>
other question would be, however, was there a test release yet? rc? was it asked to test anything? just curious
<farkuhar>
no test release that i'm aware of. If you're implying that stenur was hasty in describing dbus as "broken" on 3.7, for which there's no test release, I suppose that's a valid criticism.