From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc: replace http/git by https urls
Date: Tue, 1 Apr 2025 08:47:43 +0530
Message-ID: <52924fd8-4fe1-4335-a644-eb851130f160@gyani.pro> (raw)
In-Reply-To: <20250401000945.2371132-1-michael@niedermayer.cc>
On 2025-04-01 05:39 am, Michael Niedermayer wrote:
> These are more secure
>
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
> doc/fate_config.sh.template | 2 +-
> doc/git-howto.texi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/fate_config.sh.template b/doc/fate_config.sh.template
> index 8681805d65e..4ff8629d447 100644
> --- a/doc/fate_config.sh.template
> +++ b/doc/fate_config.sh.template
> @@ -1,5 +1,5 @@
> slot= # some unique identifier
> -repo=git://source.ffmpeg.org/ffmpeg.git # the source repository
> +repo=https://git.ffmpeg.org/ffmpeg.git # the source repository
> #branch=release/2.6 # the branch to test
> samples= # path to samples directory
> workdir= # directory in which to do all the work
> diff --git a/doc/git-howto.texi b/doc/git-howto.texi
> index 0a8d8de1d7f..e20d114f9ee 100644
> --- a/doc/git-howto.texi
> +++ b/doc/git-howto.texi
> @@ -142,7 +142,7 @@ git log <filename(s)>
> @end example
>
> You may also use the graphical tools like @command{gitview} or @command{gitk}
> -or the web interface available at @url{http://source.ffmpeg.org/}.
> +or the web interface available at @url{https://git.ffmpeg.org/ffmpeg.git}.
LGTM.
Regards,
Gyan
_______________________________________________
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-04-01 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 0:09 Michael Niedermayer
2025-04-01 3:17 ` Gyan Doshi [this message]
2025-04-01 22:34 ` Michael Niedermayer
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=52924fd8-4fe1-4335-a644-eb851130f160@gyani.pro \
--to=ffmpeg@gyani.pro \
--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