From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] http: Improve handling of Content-Range with Transfer-Encoding:chunked
Date: Wed, 9 Feb 2022 09:49:45 +0100
Message-ID: <CAPYw7P7-O3OvMCRA0jdkycp3tLFFu0TqZi73b+NjEie0AWeGhA@mail.gmail.com> (raw)
In-Reply-To: <CABLWnS83wKnNACvjs0gkhu_FMNro_t9DvvNiXYbPq8tc+f0CFw@mail.gmail.com>
On Wed, Feb 9, 2022 at 1:56 AM Vittorio Giovara <vittorio.giovara@gmail.com>
wrote:
> On Thu, Feb 3, 2022 at 3:12 PM Derek Buitenhuis <
> derek.buitenhuis@gmail.com>
> wrote:
>
> > On 2/3/2022 1:26 AM, Aman Karmani wrote:
> > > The size part of the range header is optional, and can be '*' as well.
> > >
> > > See also
> > >
> >
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20211005233244.37582-1-ffmpeg@tmm1.net/
> >
> > Isn't this an orthogonal problem to what this patch is changing?
> >
> > - Derek
> > _______________________________________________
> >
>
> Are there any other comments/objections to the patchset?
>
Nope. Just apply it.
> Thanks
> --
> Vittorio
> _______________________________________________
> 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:[~2022-02-09 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 23:49 Vittorio Giovara
2022-02-02 23:49 ` [FFmpeg-devel] [PATCH 2/2] http: Send a Range header even when the offset is 0 Vittorio Giovara
2022-02-03 1:26 ` [FFmpeg-devel] [PATCH 1/2] http: Improve handling of Content-Range with Transfer-Encoding:chunked Aman Karmani
2022-02-03 14:12 ` Derek Buitenhuis
2022-02-09 0:55 ` Vittorio Giovara
2022-02-09 8:49 ` Paul B Mahol [this message]
2022-02-11 12:02 ` Vittorio Giovara
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=CAPYw7P7-O3OvMCRA0jdkycp3tLFFu0TqZi73b+NjEie0AWeGhA@mail.gmail.com \
--to=onemda@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