From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FATE Errors
Date: Sat, 30 Apr 2022 19:25:25 +0000
Message-ID: <DM8P223MB0365E6BFBC5BB76B051C133ABAFF9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <MN2PR18MB3328824618E84EF038480D1BD3FF9@MN2PR18MB3328.namprd18.prod.outlook.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Felix LeClair
> Sent: Saturday, April 30, 2022 9:22 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] FATE Errors
>
> Both times I’ve encountered were on PopOS (think Debian/Ubuntu meets
> arch like timing release)
VM or bare metal installation?
PS: The people here don't like top-posting
Thanks,
softworkz
_______________________________________________
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-30 19:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 18:54 Soft Works
2022-04-30 19:01 ` Felix LeClair
2022-04-30 19:07 ` Soft Works
2022-04-30 19:06 ` Andreas Rheinhardt
2022-04-30 19:09 ` James Almer
2022-04-30 19:19 ` Soft Works
2022-04-30 19:22 ` Felix LeClair
2022-04-30 19:25 ` Soft Works [this message]
2022-04-30 19:31 ` Felix LeClair
2022-04-30 19:33 ` James Almer
2022-04-30 19:39 ` Soft Works
2022-04-30 20:02 ` Andreas Rheinhardt
2022-05-27 21:10 ` Soft Works
2022-05-28 7:25 ` Paul B Mahol
2022-05-28 7:26 ` Soft Works
2022-05-28 7:34 ` Paul B Mahol
2022-05-28 7:47 ` Soft Works
2022-05-28 8:04 ` Paul B Mahol
2022-05-28 8:12 ` Soft Works
2022-05-28 8:33 ` Paul B Mahol
2022-05-28 8:41 ` Soft Works
2022-05-28 8:50 ` Paul B Mahol
2022-05-28 8:57 ` Soft Works
2022-04-30 19:12 ` Soft Works
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=DM8P223MB0365E6BFBC5BB76B051C133ABAFF9@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