Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Guidance needed for a semi-breaking change
Date: Wed, 27 Apr 2022 15:18:36 +0200
Message-ID: <YmlCrL0HHgxOGc8N@phare.normalesup.org> (raw)
In-Reply-To: <5cb6218e-8647-0817-fd8f-aa815d3bf30a@rothenpieler.org>


[-- Attachment #1.1: Type: text/plain, Size: 407 bytes --]

Timo Rothenpieler (12022-04-27):
> Any existing commandline should produce the exact same output after the
> change.

I do not agree.

Small changes in default behavior are acceptable, since the user did not
specify what they want.

(I would argue that changes that fix a bug and changes that are
unambiguously and exclusively an improvement are acceptable.)

Regards,

-- 
  Nicolas George

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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".

  reply	other threads:[~2022-04-27 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 12:42 MCC CS
2022-04-27 12:49 ` Timo Rothenpieler
2022-04-27 13:06   ` MCC CS
2022-04-27 13:15     ` Timo Rothenpieler
2022-04-27 13:18       ` Nicolas George [this message]
2022-04-27 14:07         ` MCC CS
2022-04-27 15:18           ` Timo Rothenpieler
2022-04-27 18:05             ` MCC CS

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=YmlCrL0HHgxOGc8N@phare.normalesup.org \
    --to=george@nsup.org \
    --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