2018-03-09 0:02 GMT+01:00, Lou Logan :
> On Thu, 8 Mar 2018 23:37:19 +0100
> Carl Eugen Hoyos wrote:
>> diff --git a/src/download b/src/download
>> index 6783c35..b03e3d0 100644
>> --- a/src/download
>> +++ b/src/download
>> @@ -143,7 +143,7 @@
>>
>>Snapshot
>>
On 3/8/2018 8:14 PM, Lou Logan wrote:
> On Thu, Mar 8, 2018, at 2:09 PM, wm4 wrote:
>> I didn't even know about it. Can someone make http://git.ffmpeg.org
>> redirect to this as well, instead of having it return 403?
>
> While we're at it redirecting the http *.ffmpeg.org to https would be nice
>
On Thu, Mar 8, 2018, at 2:09 PM, wm4 wrote:
> I didn't even know about it. Can someone make http://git.ffmpeg.org
> redirect to this as well, instead of having it return 403?
While we're at it redirecting the http *.ffmpeg.org to https would be nice too.
___
On Thu, 8 Mar 2018 23:37:19 +0100
Carl Eugen Hoyos wrote:
> Hi!
>
> Is there a reason why we point users to another website to browse the
> FFmpeg repository?
I didn't even know about it. Can someone make http://git.ffmpeg.org
redirect to this as well, instead of having it return 403?
_
On Thu, 8 Mar 2018 23:37:19 +0100
Carl Eugen Hoyos wrote:
> Hi!
>
> Is there a reason why we point users to another website to browse the
> FFmpeg repository?
My guess is fa2da62:
src/download: use a https based link for main "Browse" button
But git.ffmpeg.org now has HTTPS so it's a moot point
