[FFmpeg-devel] [PATCH] doc/developer: use https instead of http

Ganesh Ajjanagadde gajjanagadde at gmail.com
Wed Oct 7 05:15:49 CEST 2015

Change to https for FFmpeg websites.

Signed-off-by: Ganesh Ajjanagadde <gajjanagadde at gmail.com>
 doc/developer.texi | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index 4d0fc9f..31952d8 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -28,7 +28,7 @@ this document.
 For more detailed legal information about the use of FFmpeg in
 external programs read the @file{LICENSE} file in the source tree and
-consult @url{http://ffmpeg.org/legal.html}.
+consult @url{https://ffmpeg.org/legal.html}.
 @section Contributing
@@ -436,7 +436,7 @@ Also please if you send several patches, send each patch as a separate mail,
 do not attach several unrelated patches to the same mail.
 Patches should be posted to the
- at uref{http://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
+ at uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
 mailing list. Use @code{git send-email} when possible since it will properly
 send patches without requiring extra care. If you cannot, then send patches
 as base64-encoded attachments, so your patch is not trashed during
@@ -551,7 +551,7 @@ amounts of memory when fed damaged data.
 Did you test your decoder or demuxer against sample files?
-Samples may be obtained at @url{http://samples.ffmpeg.org}.
+Samples may be obtained at @url{https://samples.ffmpeg.org}.
 Does the patch not mix functional and cosmetic changes?
@@ -718,7 +718,7 @@ FFmpeg maintains a set of @strong{release branches}, which are the
 recommended deliverable for system integrators and distributors (such as
 Linux distributions, etc.). At regular times, a @strong{release
 manager} prepares, tests and publishes tarballs on the
- at url{http://ffmpeg.org} website.
+ at url{https://ffmpeg.org} website.
 There are two kinds of releases:
@@ -797,7 +797,7 @@ Prepare the release tarballs in @code{bz2} and @code{gz} formats, and
 supplementing files that contain @code{gpg} signatures
-Publish the tarballs at @url{http://ffmpeg.org/releases}. Create and
+Publish the tarballs at @url{https://ffmpeg.org/releases}. Create and
 push an annotated tag in the form @code{nX}, with @code{X}
 containing the version number.

More information about the ffmpeg-devel mailing list