[01:25:44] *** Quits: Horwitz (~mich1@p200300ec9f3c6900022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 240 seconds)
[02:28:34] *** Joins: Horwitz (~mich1@p200300ec9f01d800022268fffe64e7c4.dip0.t-ipconnect.de)
[02:28:34] *** ChanServ sets mode: +o Horwitz
[02:28:34] *** Quits: jkoan (~jkoan@pizarro.uberspace.de) (Ping timeout: 244 seconds)
[02:28:34] *** Quits: NavitLogger (~NavitLogg@pizarro.uberspace.de) (Will I dream?)
[02:29:34] *** Joins: NavitLogger (~NavitLogg@pizarro.uberspace.de)
[02:29:34] *** Server sets mode: +nrtz 
[08:53:11] <Navit> <ilovekiruna> hi all
[15:22:10] <Navit> <jkoan> hi @ilovekiruna
[15:51:13] *** Joins: ilovekiruna (~ilovekiru@ip1f129c09.dynamic.kabel-deutschland.de)
[15:51:13] *** ChanServ sets mode: +v ilovekiruna
[15:51:21] <ilovekiruna> hi jkoan
[15:57:19] <NavitLogger> Failed: build (#22571; push) in navit-gps/navit (pull/987) -- https://circleci.com/gh/navit-gps/navit/22571?utm_campaign=chatroom-integration&amp;utm_medium=referral&amp;utm_source=irc
[18:59:55] <Navit> <jkoan> @ilovekiruna the VersionCode RP now has the "every 15min"-Format. What are your thoughts about this versus the "every 5min"-Format?
[19:16:16] <Navit> <ilovekiruna> how do we push it down to 5 min?
[19:17:44] <Navit> <jkoan> yyyyMMttFF tt = dd * 3 + HH / 8 FF = (HH % 8) * 12 + mm / 5
[19:18:00] <Navit> <jkoan> and i dont think this is really readable
[20:44:10] <Navit> <ilovekiruna> have you written that in gh issue?
[20:48:22] <Navit> <jkoan> more or less, yes
[23:16:05] <Navit> <ilovekiruna> I also find it not very intuitive
[23:16:28] <Navit> <ilovekiruna> and I believe this should be the goal of our version scheme
[23:16:33] <Navit> <ilovekiruna> being readable