All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@denx.de>, <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] CIP IRC weekly meeting today on libera.chat
Date: Wed, 13 Apr 2022 11:12:24 +0200	[thread overview]
Message-ID: <54e32f3a-cc78-2e6f-2414-9ee2e2791243@siemens.com> (raw)
In-Reply-To: <20220407090607.GA20233@duo.ucw.cz>

On 07.04.22 11:06, Pavel Machek wrote:
> Hi!
> 
>> Kindly be reminded to attend the weekly meeting through IRC to discuss
>> technical topics with CIP kernel today. Our channel is the following:
>>
>>     irc:irc.libera.chat:6667/cip
>>
>> The IRC meeting is scheduled to UTC (GMT) 13:00:
>>
>> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=4&day=7&hour=13&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248
>>
>> USWest    USEast    UK        DE        TW        JP
>> 06:00     09:00     14:00     15:00     21:00     22:00
>>
>> Last meeting minutes:
>> https://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-17-13.00.log.html
> ...
>> IMPORTANT NOTE: I'm unfortunately not able to run the meeting myself 
>> today due to an appointment conflict (damn DST...). Could someone else 
>> from the kernel team take over again? Thanks in advance.
> 
> After DST shift, 13 UTC is not really great time for me, either. 12
> UTC would be better, 9 or 10 UTC would be even better. I don't propose
> shifting today's meeting, but should we talk about shift?
> 

Forgot to follow up on this:

Are there any concerns among our participants to move this by one hour
earlier?

If no, the next logical question would then be:

Stick with one hour earlier, or will this cause conflicts again on the
end of DST in Autumn?

Please raise you voice.

Thanks,
Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2022-04-13 15:48 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  6:49 CIP IRC weekly meeting today on libera.chat Jan Kiszka
2022-04-07  9:06 ` [cip-dev] " Pavel Machek
2022-04-13  9:12   ` Jan Kiszka [this message]
2022-04-13 20:32     ` Pavel Machek
2022-04-13 23:28     ` Masami Ichikawa
2022-04-14  0:07     ` nobuhiro1.iwamatsu
2022-04-14  6:33     ` Alice Ferrazzi
  -- strict thread matches above, loose matches on Subject: below --
2024-05-16  5:24 Jan Kiszka
2024-05-16  6:56 ` [cip-dev] " Ulrich Hecht
2024-05-16 12:03 ` nobuhiro1.iwamatsu
2024-05-09  6:42 Pavel Machek
2024-05-02  9:13 Jan Kiszka
2024-05-02 12:16 ` [cip-dev] " Masami Ichikawa
2024-04-25  6:41 Jan Kiszka
2024-04-25 12:12 ` [cip-dev] " nobuhiro1.iwamatsu
2024-04-25 18:18   ` Gylstorff Quirin
2024-02-15  7:25 Jan Kiszka
2024-02-15 13:00 ` [cip-dev] " nobuhiro1.iwamatsu
2024-01-04  7:07 Jan Kiszka
2024-01-04  9:11 ` [cip-dev] " Nobuhiro Iwamatsu
2023-12-14  8:13 Jan Kiszka
2023-12-14  8:45 ` [cip-dev] " Masami Ichikawa
2023-12-14 13:05 ` nobuhiro1.iwamatsu
2023-12-07  3:50 Jan Kiszka
2023-12-07  7:26 ` [cip-dev] " nobuhiro1.iwamatsu
2023-12-07 11:05   ` Pavel Machek
2023-12-07 13:10     ` nobuhiro1.iwamatsu
2023-12-07 17:59       ` Pavel Machek
2023-12-07 12:11   ` Jan Kiszka
2023-11-23 12:39 Pavel Machek
2023-11-16  7:53 Jan Kiszka
2023-11-16  8:09 ` [cip-dev] " Chris Paterson
2023-10-19  6:26 Jan Kiszka
2023-10-19  6:47 ` [cip-dev] " Masami Ichikawa
2023-09-21  8:00 Jan Kiszka
2023-09-21 10:40 ` [cip-dev] " Pavel Machek
2023-09-07  5:46 Jan Kiszka
2023-09-07  6:07 ` [cip-dev] " Masami Ichikawa
2023-09-07  7:53 ` Chris Paterson
2023-08-17  6:04 Jan Kiszka
2023-08-17  8:25 ` [cip-dev] " Ulrich Hecht
     [not found] <1775B7580F6019BC.31298@lists.cip-project.org>
2023-08-03 11:59 ` Pavel Machek
2023-06-08  6:08 Jan Kiszka
2023-06-08  8:58 ` [cip-dev] " Ulrich Hecht
2023-05-04  6:49 Jan Kiszka
2023-05-04  8:39 ` [cip-dev] " Nobuhiro Iwamatsu
2023-04-13  7:00 Jan Kiszka
2023-04-13 20:59 ` [cip-dev] " Pavel Machek
2023-02-23  6:49 Jan Kiszka
2023-02-23 11:31 ` [cip-dev] " Chris Paterson
2023-01-05  7:03 Jan Kiszka
2023-01-05 15:41 ` [cip-dev] " Pavel Machek
2022-12-15  6:19 Jan Kiszka
2022-12-15 10:56 ` [cip-dev] " Chris Paterson
2022-11-10  7:16 Jan Kiszka
2022-11-10  7:28 ` [cip-dev] " Masami Ichikawa
2022-11-03  6:58 Jan Kiszka
2022-11-03 10:59 ` [cip-dev] " Chris Paterson
2022-08-18  0:44 Masami Ichikawa
2022-08-18  8:43 ` [cip-dev] " Ulrich Hecht
2022-07-28  7:11 Jan Kiszka
2022-07-28 10:20 ` [cip-dev] " Chris Paterson
2022-06-16  6:45 Jan Kiszka
2022-06-16  6:49 ` [cip-dev] " Ulrich Hecht
2022-05-12  6:10 Jan Kiszka
2022-05-12  6:51 ` [cip-dev] " Chris Paterson
2022-05-12 11:17 ` Pavel Machek
2022-03-03  6:32 Jan Kiszka
2022-02-24  8:39 Jan Kiszka
2022-02-17  7:49 Jan Kiszka
2022-02-10  7:07 Jan Kiszka
2022-02-03  6:21 Jan Kiszka
2022-02-03 18:25 ` Pavel Machek
2022-01-20  5:34 Alice Ferrazzi
2021-12-16  7:40 Jan Kiszka
2021-12-16  9:40 ` nobuhiro1.iwamatsu
2021-12-09  7:45 Jan Kiszka
2021-12-09  8:11 ` Chris Paterson
2021-12-02  7:29 Jan Kiszka
2021-11-25  7:12 Jan Kiszka
2021-11-18  7:31 Jan Kiszka
2021-11-11  7:25 Jan Kiszka
2021-11-04  7:40 Jan Kiszka
2021-11-04 19:36 ` Pavel Machek
2021-10-28  6:18 Jan Kiszka
2021-10-28 18:37 ` Pavel Machek
2021-10-21  6:24 Jan Kiszka
2021-10-14  6:10 Jan Kiszka
2021-10-07  6:38 Jan Kiszka
2021-10-07  6:38 ` Jan Kiszka
2021-09-16  6:11 Jan Kiszka
2021-09-16 12:04 ` Chris Paterson
2021-09-09  6:47 Jan Kiszka
2021-09-02  5:41 Jan Kiszka
2021-08-26  0:04 masashi.kudo
2021-08-19  1:00 masashi.kudo
2021-08-11 23:31 masashi.kudo
2021-08-04 22:37 masashi.kudo
2021-07-29  1:30 masashi.kudo
2021-07-22  1:30 masashi.kudo
2021-07-15  2:34 masashi.kudo
2021-07-07 22:54 masashi.kudo
2021-07-01  1:51 masashi.kudo
2021-06-23 23:49 masashi.kudo
2021-06-17  1:29 masashi.kudo
2021-06-17  6:49 ` Pavel Machek
2021-06-03  1:28 masashi.kudo
2021-06-04 19:35 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54e32f3a-cc78-2e6f-2414-9ee2e2791243@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=pavel@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.