From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v13 1/1] avformat: Add IPFS protocol support.
Date: Sun, 10 Apr 2022 16:41:27 +0200
Message-ID: <20220410144127.GD2829255@pb2> (raw)
In-Reply-To: <20220406120056.10537-2-markg85@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
On Wed, Apr 06, 2022 at 02:00:56PM +0200, Mark Gaiser wrote:
[...]
> + if (stat_ret < 0) {
> + av_log(h, AV_LOG_INFO, "Unable to find IPFS folder. We tried:\n");
> + av_log(h, AV_LOG_INFO, "- $IPFS_PATH, which was empty.\n");
> + av_log(h, AV_LOG_INFO, "- $HOME/.ipfs (full uri: %s) which doesn't exist.\n", ipfs_full_data_folder);
The 3 av_log() can also be combined
If nothing else is found then ill change that myself and apply in a day or 2
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".
next prev parent reply other threads:[~2022-04-10 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:00 [FFmpeg-devel] [PATCH v13 0/1] " Mark Gaiser
2022-04-06 12:00 ` [FFmpeg-devel] [PATCH v13 1/1] avformat: " Mark Gaiser
2022-04-07 22:01 ` Mark Gaiser
2022-04-10 14:41 ` Michael Niedermayer [this message]
2022-04-11 13:46 ` Mark Gaiser
2022-04-12 18:02 ` Michael Niedermayer
2022-04-12 18:43 ` Mark Gaiser
2022-04-12 23:09 ` James Almer
2022-04-12 23:23 ` Mark Gaiser
2022-04-13 12:28 ` Andreas Rheinhardt
2022-04-13 13:14 ` Mark Gaiser
2022-04-13 14:45 ` Hendrik Leppkes
2022-04-13 15:13 ` Mark Gaiser
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=20220410144127.GD2829255@pb2 \
--to=michael@niedermayer.cc \
--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