| *** Mikaela is now known as Guest2227 | 00:07 | |
| pvuorela | dcaliste: hey | 09:01 |
|---|---|---|
| dcaliste | Good morning pvuorela. | 09:01 |
| dcaliste | Thanks for merging the DST fix yesterday. | 09:02 |
| pvuorela | sure, thanks for the PR. | 09:03 |
| pvuorela | the thisandlater i'm about to merge nowish. | 09:03 |
| dcaliste | Do you think it will have time to go in a new RC before the release ? | 09:03 |
| pvuorela | which one? | 09:04 |
| dcaliste | The DST fix, I mean. | 09:04 |
| pvuorela | hm. not sure. we should be wrapping up the release and it's not a regression. though it is a simple change. | 09:04 |
| dcaliste | I understand, do as best as it can be done knowing the release planning. | 09:06 |
| pvuorela | yea, i'm somewhere in the middle of whether to include or not. | 09:06 |
| dcaliste | About the mkcal thisandfuture, I noticed that I forgot to bump the version in the spec. I know that you'll tag and the builder will take it, but do you want me to quickly amend the PR ? | 09:07 |
| pvuorela | doesn't matter much. no objections if you want. | 09:07 |
| dcaliste | Yeh, I've pushed the version change. It's easier for me since I build in the SDK and the generated RPM has the spec version. Then, in jolla-calendar when I bump the requires in the spec, there is no complain when I install. | 09:10 |
| dcaliste | Not a big bdeal, I can still force installation of rpms, but it's cleaner like that. | 09:10 |
| pvuorela | yep, helps with self-built packages. | 09:10 |
| dcaliste | I don't know if you had time to look at the silica PR on the AutoFill bug for the location entry for events in calendar ? | 09:13 |
| pvuorela | ah, sorry. that one i forgot existed. | 09:13 |
| pvuorela | adding to my todo list | 09:13 |
| dcaliste | Thanks, some thoughts when you'll review it : I'm wondering in the initial design why saving one AutoFill is trigerring save for all autofill ? Was it in case different entries use the same autofill database file and it must be kept in sync ? | 09:14 |
| pvuorela | alright. no immediate idea :) | 09:16 |
| dcaliste | Hopefully I'm not disturbing too much and the PR is not a bug fix, so no hurry, but I'm also wondering if mkcal#40 is a good idea or not. It tries to hide internal exception implementation in mkcal from clients. But it comes with the cost that in the callback of a save, the reported inxcidence may not be part of the calendar… | 09:19 |
| *** Mikaela is now known as Guest2269 | 09:22 | |
| dcaliste | To finish, thanks for reporting internally the issue with the email feedback. | 09:24 |
| pvuorela | seemed messy indeed. hoping jusa would have some time soon to make it saner. | 09:26 |
| dcaliste | If he's too busy, you may grant me access to the closed source config repo, I may try to propose something and he'll review. | 09:27 |
| pvuorela | let's see. there could be an option to merge the different open and closed configs too, and would rather have jusa do that. | 09:28 |
| dcaliste | Sure, I agree. | 09:29 |
| dcaliste | Thank you for the meeting today. I'm attending another one on lithium insertion in graphite now. Thanks also for the various reviews. See you. | 09:30 |
| pvuorela | nice :) thanks and see you! | 09:32 |
| henk | anyone here using a pebble (time steel in particular maybe?) with sailfish and can tell me if that works well and what to expect to not work? | 20:14 |
| b100dian[m] | https://openrepos.net/comment/41261#comment-41261 Time steel seems to work :) | 20:19 |
| henk | yes, and a maintained app, which is nice | 20:27 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!