Chiebot-Mirror
/
FFmpeg
mirror of https://github.com/FFmpeg/FFmpeg.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc/developer: use https instead of http

Browse Source 
Change to https for FFmpeg websites.

Signed-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
pull/154/head
Ganesh Ajjanagadde 9 years ago committed by Michael Niedermayer
parent a852db796e
commit 2d8ef1b690
1 changed files with 5 additions and 5 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 10
      doc/developer.texi

10
doc/developer.texi
Unescape View File

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

Write Preview
Loading…
Cancel
Save