From: Thilo Borgmann <thilo.borgmann@mail.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc: Merge doc/dev_community/* and Code of Conduct into a seperate file
Date: Wed, 8 Feb 2023 16:52:01 +0100
Message-ID: <2e42bad0-5c38-c2e1-731e-ecc9e95b6ab3@mail.de> (raw)
In-Reply-To: <20230208154549.42075-1-thilo.borgmann@mail.de>
Am 08.02.23 um 16:45 schrieb Thilo Borgmann:
> Remove doc/dev_communit markup files completely as they are at the wrong place.
> Create a new community page, merging all of doc/dev_community and subsection Code of Conduct into a common place.
> The corresponding patch to ffmpeg-web puts the Organisation & Code of Conduct into a seperate community chapter on the FFmpeg website.
> ---
> doc/Makefile | 1 +
> doc/community.texi | 169 ++++++++++++++++++++++++
> doc/dev_community/community.md | 83 ------------
> doc/dev_community/resolution_process.md | 91 -------------
> doc/developer.texi | 29 ----
> doc/mailing-list-faq.texi | 2 +-
> 6 files changed, 171 insertions(+), 204 deletions(-)
> create mode 100644 doc/community.texi
> delete mode 100644 doc/dev_community/community.md
> delete mode 100644 doc/dev_community/resolution_process.md
Pls ignore this, a patchset replacing this had been submitted to -devel.
-Thilo
_______________________________________________
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:[~2023-02-08 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:45 Thilo Borgmann
2023-02-08 15:52 ` Thilo Borgmann [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=2e42bad0-5c38-c2e1-731e-ecc9e95b6ab3@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