From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Libera.chat irc logs
Date: Mon, 7 Feb 2022 11:53:44 +0100
Message-ID: <20220207105344.GS2829255@pb2> (raw)
In-Reply-To: <AM7PR03MB66608AA1E0327AD959BF62008F2B9@AM7PR03MB6660.eurprd03.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1026 bytes --]
On Sun, Feb 06, 2022 at 10:36:41AM +0100, Andreas Rheinhardt wrote:
> Gyan Doshi:
> >
> > In our documentation, we state
> >
> > 'Our IRC channels are publically logged and archives of both channels
> > can be viewed at ffmpeg-devel-irc.'
> >
> > However, the archives in the link end with June 2020 i.e. at the time of
> > the Libera switchover. The topic for #ffmpeg-devel at Libera does
> > include "This channel is publicly logged".
> >
> > Where do we host logs for chats on Libera?
> >
> > Regards,
> > Gyan
>
> The logs stopped way before the libera switchover (which was only in
> 2021, not June 2020). There were issues even before then.
if someone can setup a new (more reliable) IRC log bot which sends
mails to the ffmpeg-devel-irc ML. That would be welcome
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-02-07 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 9:21 Gyan Doshi
2022-02-06 9:36 ` Andreas Rheinhardt
2022-02-07 10:53 ` Michael Niedermayer [this message]
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=20220207105344.GS2829255@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git