Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Collective Ping
Date: Sun, 5 Jun 2022 22:35:51 +0000
Message-ID: <DM8P223MB03653F10ED62E6A8C0D82F5BBAA39@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)

Hello,

I’d like to kindly PING about the following submissions.


libavformat/asf: fix handling of byte array length values
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=6653
=> No pending questions or objections


Add derive-device function which searches for existing devices in both directions
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=6655
=> pending review from Mark Thompson


Support long file names on Windows
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=6701
=> No pending questions or objections


libx264: Set min build version to 158
https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.30.v6.ffstaging.FFmpeg.1653568143191.ffmpegagent@gmail.com/
=> No pending questions or objections


avcodec/dvdsubdec, dvbsubdec: remove bitmap dumping in DEBUG builds
https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.17.v3.ffstaging.FFmpeg.1653749538475.ffmpegagent@gmail.com/
=> No pending questions or objections


libavutil/tests/md5: Remove 'volatile workaround' to avoid warnings
https://patchwork.ffmpeg.org/project/ffmpeg/patch/pull.20.v4.ffstaging.FFmpeg.1653750420780.ffmpegagent@gmail.com/
=> No pending questions or objections


Please let me know whether there are any questions or concerns left
with any of the above.

Thanks,
sw



_______________________________________________
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-06-05 22:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DM8P223MB03653F10ED62E6A8C0D82F5BBAA39@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.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