IRC logs for #cip for Thursday, 2022-03-31

« Wednesday, 2022-03-30 Index Friday, 2022-04-01 »
*** jimmychen <jimmychen!~jimmychen@123.51.235.192> has joined #cip05:26
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip05:57
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip06:51
*** toscalix <toscalix!~toscalix@213.red-79-144-153.dynamicip.rima-tde.net> has joined #cip07:54
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip09:07
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC10:58
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC11:02
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip11:08
*** uli <uli!~uli@55d46fed.access.ecotel.net> has joined #cip11:09
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip11:14
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC12:20
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has joined #cip12:38
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip12:58
*** pave1 <pave1!~pavel@88.103.226.95> has joined #cip12:59
pave1#startmeeting CIP IRC weekly meeting13:00
brlogger`Meeting started Thu Mar 31 13:00:31 2022 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
collab-meetbotMeeting started Thu Mar 31 13:00:31 2022 UTC and is due to finish in 60 minutes.  The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
pave1Hello, everyone!13:00
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip13:00
ulihello13:01
pave1And hello, robots. Seems that we have two of them today :-).13:01
patersonc[m]Hello13:01
masamihi13:01
alicefHi13:02
pave1Ok, let's get started13:03
pave1#topic AI review13:03
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
pave11. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm13:03
patersonc[m]No updates on this13:03
pave1Ok. There are no other AIs...?13:04
pave1313:04
pave1213:04
pave1113:04
pave1#topic Kernel maintenance updates13:04
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:04
ulireviewed 5.10.10913:04
pave1I have reviewed patches for 5.10.109/110, and am working on 4.4-rt.13:04
masamiThis week reported 6 new CVEs. Most of them are fixed and these are not serious issues13:05
pave1Yes, thanks for the report.13:05
masamipavel: :-)13:06
pave1We don't have Iwamatsu-san here...13:06
pave1If he reappears we can re-visit.13:06
pave1313:06
pave1213:06
pave1113:07
pave1#topic Kernel testing13:07
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:07
pave1patersonc: Floor is yours :-).13:07
patersonc[m]I'm not sure there are many updates tbh13:08
pave1No updates are good updates :-).13:08
pave1313:08
pave1213:08
pave1113:08
alicefNo iPad13:08
alicefNo update from me13:09
alicefSorry autocorrection13:09
pave1No problem :-).13:09
pave1#topic AOB13:09
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:09
pave1There's extended TSC meeting on 4th of April.13:09
pave1Anything else?13:10
patersonc[m]We've had a few visitors to this IRC channel recently, but not many people are ever online. Could we change the channel topic to point people towards the cip-dev mailing  list?13:10
pave1patersonc: Sounds like good idea. Anyone can do that?13:10
alicefpatersonc[m]: sure13:10
alicefI will13:10
patersonc[m]Thanks13:11
patersonc[m]We'd need to find a way to reset it after the bots stop playing with it in the meetings13:11
pave1I guess reasonable information would be "go to cip-dev for discussion" and "we are here at thursday if you want irc"...13:11
alicefUsually it automatically reset at the end afair13:12
pave1We have now two robots watching us, lets see how they fight.13:12
pave1513:12
pave1413:12
pave1313:12
pave1213:12
pave1113:12
alicefYeah also meeting time in utc iso standard13:12
alicefWill do after the meeting13:13
pave1Yes. And actually... with DST kicking in all around the world, we may want to move the meeting...?13:13
pave1I guess that's possible topic for next meeting.13:14
alicefJapan have no dst afaik13:14
pave1Wikipedia agrees with you. Does that mean that earlier start is not feasible?13:15
alicefIs ok for me13:15
masamino problems13:15
alicefCurrently is 22:1513:15
alicefJST13:16
pave1Aha, so I guess it is US that prevents earlier start, and they have DST, so move would be possible.13:16
alicefTime.is/Japan13:16
pave1I guess we should discuss that when Jan is around.13:16
alicefMaybe also iwamatsu13:16
pave1Agreed.13:17
pave1313:17
pave1213:17
pave1113:17
pave1#endmeeting13:17
collab-meetbotMeeting ended Thu Mar 31 13:17:26 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:17
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-31-13.00.html13:17
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-31-13.00.txt13:17
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-31-13.00.log.html13:17
brlogger`Meeting ended Thu Mar 31 13:17:27 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:17
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-31-13.00.html13:17
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-31-13.00.txt13:17
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-31-13.00.log.html13:17
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:17
pave1Thank you!13:17
ulithanks13:17
alicefpave1: thank you for chairing13:18
alicefThank you13:18
masamithanks!.13:18
alicefTime.is/utc13:18
*** masami <masami!~masami@FL1-119-240-125-62.tky.mesh.ad.jp> has quit IRC13:18
pave1alicef: You are welcome. I hope I did well.13:18
alicefyup13:19
*** pave1 <pave1!~pavel@88.103.226.95> has quit IRC13:22
*** ChanServ sets mode: +o alicef13:31
*** alicef changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/ | you can find the CIP mailing list here https://lists.cip-project.org/g/cip-dev | CIP kernel meeting are every Thursday at 13:00 UTC"13:31
*** alicef changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://irclogs.baserock.org/cip/""13:33
patersonc[m]Thanks alicef :)13:34
alicefsounds good the new topic ?13:34
patersonc[m]Sure :)13:35
alicefthx13:35
*** ChanServ sets mode: -o alicef13:35
alicefpatersonc[m]: the topic is already automatically resetted after the bot play with it13:47
alicefis by default13:47
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:10
*** toscalix <toscalix!~toscalix@213.red-79-144-153.dynamicip.rima-tde.net> has quit IRC17:16
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC18:15
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC21:51
« Wednesday, 2022-03-30 Index Friday, 2022-04-01 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!