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] [PATCH 1/2] lavf/avio: add avio_vprintf()
Date: Sun, 12 Jun 2022 19:00:41 +0200
Message-ID: <YqYbufb4SARtjGOa@phare.normalesup.org> (raw)
In-Reply-To: <20220612153210.GB11679@mariano>


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

Stefano Sabatini (12022-06-12):
> Updated.

Hi. Since it is somewhat related, I would appreciate if you gave your
opinion on the option of having a good string API in FFmpeg:

https://ffmpeg.org/pipermail/ffmpeg-devel/2021-December/290226.html

Eventually, I would like to have the more generic writers from ffprobe
(JSON, XML) in lavu to be used by diagnostic filters. But I will not be
doing that with pedestrian strings.

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-06-12 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210418213058.24475-1-stefasab@gmail.com>
     [not found] ` <20210421215335.GC12140@mariano>
2022-04-03 14:03   ` Stefano Sabatini
2022-06-09 19:03     ` Marton Balint
2022-06-12 15:32       ` Stefano Sabatini
2022-06-12 17:00         ` Nicolas George [this message]
2022-06-16 16:23           ` Soft Works
     [not found] ` <20210418213058.24475-2-stefasab@gmail.com>
     [not found]   ` <20210419092649.GJ4777@pb2>
     [not found]     ` <20210421215704.GD12140@mariano>
2022-04-03 14:06       ` [FFmpeg-devel] [PATCH 2/2] ffprobe: add -o option Stefano Sabatini
2022-06-09 19:09         ` Marton Balint
2022-06-12 15:33           ` Stefano Sabatini
2022-06-13 20:47             ` Marton Balint

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=YqYbufb4SARtjGOa@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