Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Make tests a requirement
Date: Tue, 04 Jul 2023 01:31:49 +0200
Message-ID: <9717723743763a0717ac3affcff202ad99c71250.camel@haerdin.se> (raw)
In-Reply-To: <20230703230005.7755-1-michael@niedermayer.cc>

tis 2023-07-04 klockan 01:00 +0200 skrev Michael Niedermayer:
> Suggested-by: Anton
> 
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
>  doc/developer.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 0c2f2cd7d1..67f7f78e86 100644
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -806,7 +806,7 @@ improves readability.
>  
>  @item
>  Consider adding a regression test for your code. All new modules
> -should be covered by tests. That includes demuxers, muxers,
> decoders, encoders
> +must be covered by tests. That includes demuxers, muxers, decoders,
> encoders

+1

/Tomas
_______________________________________________
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".

  reply	other threads:[~2023-07-03 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 23:00 Michael Niedermayer
2023-07-03 23:31 ` Tomas Härdin [this message]
2023-07-04  1:38   ` Paul B Mahol
2023-07-04  9:01     ` Tomas Härdin
2023-07-04 11:32     ` Nicolas George
2023-07-04  3:04   ` Pierre-Anthony Lemieux
2023-07-04  9:02 ` Jean-Baptiste Kempf
2023-07-04 14:56 ` Rémi Denis-Courmont

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=9717723743763a0717ac3affcff202ad99c71250.camel@haerdin.se \
    --to=git@haerdin.se \
    --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