From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/6] doc/developer: merge the 'contributing code' section into its parent chapter Date: Sun, 27 Aug 2023 14:19:56 +0200 Message-ID: <CAMcAR4rphgUr7zO6bo6YKY8CMf5NJXu9yePvNaL3-jvp8vpFUQ@mail.gmail.com> (raw) In-Reply-To: <20230826180748.15977-2-anton@khirnov.net> Il sab 26 ago 2023, 20:08 Anton Khirnov <anton@khirnov.net> ha scritto: > The section consistes of a single short paragraph linking to other > chapters. The enclosing chapter also has no other sections, all other > text is placed in the chapter directly. > Keeping a separate section for this paragraph just adds more clutter. > --- > doc/developer.texi | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/doc/developer.texi b/doc/developer.texi > index 85515f5d37..d27716ab97 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -44,8 +44,6 @@ By supporting the project you find useful you ensure it > continues to be > maintained and developed. > @end itemize > > -@section Contributing code > - > All proposed code changes should be submitted for review to > @url{mailto:ffmpeg-devel@@ffmpeg.org, the development mailing list}, as > described in more detail in the @ref{Submitting patches} chapter. The code > Lgtm, thanks. > _______________________________________________ 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:[~2023-08-27 12:20 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-26 18:07 [FFmpeg-devel] [PATCH 1/6] doc/developer: move a sentence to a more appropriate place Anton Khirnov 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 2/6] doc/developer: merge the 'contributing code' section into its parent chapter Anton Khirnov 2023-08-27 12:19 ` Stefano Sabatini [this message] 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 3/6] doc/developer: fix a nonsense statement Anton Khirnov 2023-08-27 12:21 ` Stefano Sabatini 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 4/6] doc/developer: add a code behaviour section to development policy Anton Khirnov 2023-08-26 18:36 ` Andreas Rheinhardt 2023-08-26 18:54 ` Anton Khirnov 2023-08-27 12:38 ` Stefano Sabatini 2023-08-29 8:34 ` Anton Khirnov 2023-08-31 15:28 ` Stefano Sabatini 2023-09-01 17:01 ` Michael Niedermayer 2023-09-01 17:10 ` Rémi Denis-Courmont 2023-09-01 17:26 ` Paul B Mahol 2023-09-01 18:33 ` Stefano Sabatini 2023-09-02 20:03 ` Michael Niedermayer 2023-09-03 8:29 ` Rémi Denis-Courmont 2023-09-03 16:21 ` Michael Niedermayer 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 5/6] doc/developer: drop an outdated item Anton Khirnov 2023-08-27 12:40 ` Stefano Sabatini 2023-08-26 18:07 ` [FFmpeg-devel] [PATCH 6/6] doc/developer: deduplicate commit message rules Anton Khirnov 2023-08-27 12:46 ` Stefano Sabatini 2023-08-27 12:18 ` [FFmpeg-devel] [PATCH 1/6] doc/developer: move a sentence to a more appropriate place Stefano Sabatini
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=CAMcAR4rphgUr7zO6bo6YKY8CMf5NJXu9yePvNaL3-jvp8vpFUQ@mail.gmail.com \ --to=stefasab@gmail.com \ --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