From: Efrain T <torresefrain10@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/unix: Set is_streamed to true
Date: Thu, 6 Feb 2025 02:00:53 -0600
Message-ID: <CAEjy0KTrZ3qQSryoRc+OqHc4fDqMDFHJJXGMurHiVWD75HR-ug@mail.gmail.com> (raw)
In-Reply-To: <bce2cf9f-41cc-4d20-bd30-c5567b34fdf8@gmail.com>
That sounds perfectly fine with me. Thanks for the quick reply.
On Thursday, February 6, 2025, Leo Izen <leo.izen@gmail.com> wrote:
> On 2/6/25 2:00 AM, dank074 wrote:
>
>> Currently when a Unix Domain Socket is used as input there is a loss of
>> data when data is consumed from the stream. Setting is_streamed to true
>> fixes this, since the unix domain socket is now treated like a consumable
>> stream.
>>
>> Fixes: #9346
>> Signed-off-by: dank074 <torresefrain10@gmail.com>
>> ---
>> libavformat/unix.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/libavformat/unix.c b/libavformat/unix.c
>> index 5704155cf0..2de4023835 100644
>> --- a/libavformat/unix.c
>> +++ b/libavformat/unix.c
>> @@ -89,7 +89,7 @@ static int unix_open(URLContext *h, const char
>> *filename, int flags)
>> }
>> s->fd = fd;
>> -
>> + h->is_streamed = 1;
>> return 0;
>> fail:
>>
>
> The patch looks fine as-is but two style nitpicks:
>
> - we like to have a full blank line between the return statement and the
> one before it, so you should add this line of code right after the line
> s->fd = fd; but not remove the blank line that was there
> - commit messages should be capped at 72 characters per line for
> historical reasons, so please insert newline characters in the commit
> message
>
> If there's no other objections I will push this patch and make both of
> these changes on my end, preserving authorship before I do, if that is okay
> with you.
>
> - Leo Izen (Traneptora)
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2025-02-06 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 7:00 dank074
2025-02-06 7:41 ` Leo Izen
2025-02-06 8:00 ` Efrain T [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 1:25 Efrain Torres
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=CAEjy0KTrZ3qQSryoRc+OqHc4fDqMDFHJJXGMurHiVWD75HR-ug@mail.gmail.com \
--to=torresefrain10@gmail.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