From: "Thilo Borgmann" <thilo.borgmann@mail.de>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Document the addresses of the committees (was: Contact of the Technical Committee)
Date: Tue, 02 Aug 2022 20:16:25 +0200
Message-ID: <652B396A-D633-48D9-82C2-F60F1DC9A8C5@mail.de> (raw)
In-Reply-To: <YulgQXsVNWNoCZpP@phare.normalesup.org>
On 2 Aug 2022, at 19:34, Nicolas George wrote:
> Thilo Borgman (12022-08-02):
>> Of course, thought it would already be there together with CC.
>>
>> There’s a typo in the mail address, otherwise LGTM.
>
> Indeed, locally fixed:
>
> +The TC can be contacted at <tc@ffmpeg>.
> +The CC can be contacted at <cc@ffmpeg>.
@ffmpeg.org, no?
-Thilo
>
> I will wait some time and push if nobody objects.
>
> Thanks,
>
> --
> Nicolas George
> _______________________________________________
> 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".
_______________________________________________
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".
next prev parent reply other threads:[~2022-08-02 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 15:12 [FFmpeg-devel] Contact of the Technical Committee Nicolas George
2022-07-24 19:45 ` Jean-Baptiste Kempf
2022-08-02 17:10 ` [FFmpeg-devel] [PATCH] Document the addresses of the committees (was: Contact of the Technical Committee) Nicolas George
2022-08-02 17:13 ` Thilo Borgmann
2022-08-02 17:34 ` Nicolas George
2022-08-02 18:16 ` Thilo Borgmann [this message]
2022-08-02 18:18 ` Thilo Borgmann
2022-08-02 18:15 ` Jean-Baptiste Kempf
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=652B396A-D633-48D9-82C2-F60F1DC9A8C5@mail.de \
--to=thilo.borgmann@mail.de \
--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