From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_cuda: check that the SDK defines cuCtxGetCurrent()
Date: Sat, 7 Oct 2023 12:34:43 +0200
Message-ID: <d1092b8d-b46e-42e2-9b51-15ce9addc476@rothenpieler.org> (raw)
In-Reply-To: <CA+anqdyxfwgORorfPWDmLUrw8-0yYNK_ZgSaiTdDZAkU0uSi6A@mail.gmail.com>
On 06.10.2023 18:43, Hendrik Leppkes wrote:
> On Fri, Oct 6, 2023 at 3:47 PM Timo Rothenpieler <timo@rothenpieler.org> wrote:
>> I'm quite confused why this specific instance suddenly causes so much upset.
>
> Because its bad form to break compilation of master, if all it took to
> avoid that is change the order of pushing a tag to one repo and a
> patch to another.
>
I think you are misunderstanding the versioning of the headers?
They were already on the right version, all you needed to do was update
them.
There was never a time where it was impossible to build ffmpeg.
_______________________________________________
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".
prev parent reply other threads:[~2023-10-07 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 2:06 James Almer
2023-10-01 2:24 ` James Almer
2023-10-01 11:39 ` Timo Rothenpieler
2023-10-06 12:29 ` Hendrik Leppkes
2023-10-06 13:07 ` Timo Rothenpieler
2023-10-06 13:31 ` Hendrik Leppkes
2023-10-06 13:47 ` Timo Rothenpieler
2023-10-06 16:43 ` Hendrik Leppkes
2023-10-07 10:34 ` Timo Rothenpieler [this message]
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=d1092b8d-b46e-42e2-9b51-15ce9addc476@rothenpieler.org \
--to=timo@rothenpieler.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