Commit 21de9204 authored by Johan Andersson's avatar Johan Andersson Committed by Ronald S. Bultje
Browse files

Update the url to the site website and change ffmpeg-devel to libav-devel


Signed-off-by: default avatarRonald S. Bultje <rsbultje@gmail.com>
parent 0e6a3ee4
......@@ -151,7 +151,7 @@ should also be avoided if they don't make the code easier to understand.
ask/discuss it on the developer mailing list.
@item
Do not change behavior of the programs (renaming options etc) or public
API or ABI without first discussing it on the ffmpeg-devel mailing list.
API or ABI without first discussing it on the libav-devel mailing list.
Do not remove functionality from the code. Just improve!
Note: Redundant code can be removed.
......@@ -160,7 +160,7 @@ should also be avoided if they don't make the code easier to understand.
which change behavior, defaults etc, without asking first. The same
applies to compiler warning fixes, trivial looking fixes and to code
maintained by other developers. We usually have a reason for doing things
the way we do. Send your changes as patches to the ffmpeg-devel mailing
the way we do. Send your changes as patches to the libav-devel mailing
list, and if the code maintainers say OK, you may commit. This does not
apply to files you wrote and/or maintain.
@item
......@@ -182,27 +182,27 @@ should also be avoided if they don't make the code easier to understand.
particular bug. Comments such as "fixed!" or "Changed it." are unacceptable.
@item
If you apply a patch by someone else, include the name and email address in
the log message. Since the ffmpeg-cvslog mailing list is publicly
the log message. Since the libav-commits mailing list is publicly
archived you should add some SPAM protection to the email address. Send an
answer to ffmpeg-devel (or wherever you got the patch from) saying that
answer to libav-devel (or wherever you got the patch from) saying that
you applied the patch.
@item
When applying patches that have been discussed (at length) on the mailing
list, reference the thread in the log message.
@item
Do NOT commit to code actively maintained by others without permission.
Send a patch to ffmpeg-devel instead. If no one answers within a reasonable
Send a patch to libav-devel instead. If no one answers within a reasonable
timeframe (12h for build failures and security fixes, 3 days small changes,
1 week for big patches) then commit your patch if you think it is OK.
Also note, the maintainer can simply ask for more time to review!
@item
Subscribe to the ffmpeg-cvslog mailing list. The diffs of all commits
Subscribe to the libav-commits mailing list. The diffs of all commits
are sent there and reviewed by all the other developers. Bugs and possible
improvements or general questions regarding commits are discussed there. We
expect you to react if problems with your code are uncovered.
@item
Update the documentation if you change behavior or add features. If you are
unsure how best to do this, send a patch to ffmpeg-devel, the documentation
unsure how best to do this, send a patch to libav-devel, the documentation
maintainer(s) will review and commit your stuff.
@item
Try to keep important discussions and requests (also) on the public
......@@ -261,8 +261,8 @@ verify that there are no big problems.
Patches should be posted as base64 encoded attachments (or any other
encoding which ensures that the patch will not be trashed during
transmission) to the ffmpeg-devel mailing list, see
@url{http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel}
transmission) to the libav-devel mailing list, see
@url{https://lists.libav.org/mailman/listinfo/libav-devel}
It also helps quite a bit if you tell us what the patch does (for example
'replaces lrint by lrintf'), and why (for example '*BSD isn't C99 compliant
......@@ -361,7 +361,7 @@ send a reminder by email. Your patch should eventually be dealt with.
If the patch fixes a bug, did you provide enough information, including
a sample, so the bug can be reproduced and the fix can be verified?
Note please do not attach samples >100k to mails but rather provide a
URL, you can upload to ftp://upload.ffmpeg.org
URL, you can upload to ftp://upload.libav.org
@item
Did you provide a verbose summary about what the patch does change?
@item
......@@ -387,7 +387,7 @@ send a reminder by email. Your patch should eventually be dealt with.
@section Patch review process
All patches posted to ffmpeg-devel will be reviewed, unless they contain a
All patches posted to libav-devel will be reviewed, unless they contain a
clear note that the patch is not for the git master branch.
Reviews and comments will be posted as replies to the patch on the
mailing list. The patch submitter then has to take care of every comment,
......
......@@ -25,7 +25,7 @@ Nowhere. We do not support old FFmpeg versions in any way, we simply lack
the time, motivation and manpower to do so. If you have a problem with an
old version of FFmpeg, upgrade to the latest Subversion snapshot. If you
still experience the problem, then you can report it according to the
guidelines in @url{http://ffmpeg.org/bugreports.html}.
guidelines in @url{http://libav.org/bugreports.html}.
@section Why doesn't FFmpeg support feature [xyz]?
......@@ -40,13 +40,13 @@ No. Windows DLLs are not portable, bloated and often slow.
Moreover FFmpeg strives to support all codecs natively.
A DLL loader is not conducive to that goal.
@section My bug report/mail to ffmpeg-devel/user has not received any replies.
@section My bug report/mail to libav-devel/user has not received any replies.
Likely reasons
@itemize
@item We are busy and haven't had time yet to read your report or
investigate the issue.
@item You didn't follow @url{http://ffmpeg.org/bugreports.html}.
@item You didn't follow @url{http://libav.org/bugreports.html}.
@item You didn't use Subversion HEAD.
@item You reported a segmentation fault without gdb output.
@item You describe a problem but not how to reproduce it.
......@@ -124,7 +124,7 @@ problem and an NP-hard problem...
@section ffmpeg does not work; what is wrong?
Try a @code{make distclean} in the ffmpeg source directory before the build. If this does not help see
(@url{http://ffmpeg.org/bugreports.html}).
(@url{http://libav.org/bugreports.html}).
@section How do I encode single pictures into movies?
......
......@@ -371,7 +371,7 @@ ACL allow 192.168.0.0 192.168.255.255
# Redirect index.html to the appropriate site
<Redirect index.html>
URL http://www.ffmpeg.org/
URL http://www.libav.org/
</Redirect>
......@@ -44,11 +44,11 @@ I. BASICS:
1. Cloning the source tree:
git clone git://git.ffmpeg.org/ffmpeg.git <target>
git clone git://git.libav.org/libav.git <target>
This will put the FFmpeg sources into the directory <target>.
git clone git@git.ffmpeg.org:ffmpeg.git <target>
git clone git@git.libav.org:libav.git <target>
This will put the FFmpeg sources into the directory <target> and let
you push back your changes to the remote repository.
......@@ -97,7 +97,7 @@ I. BASICS:
git log <filename(s)>
You may also use the graphical tools like gitview or gitk or the web
interface available at http://git.ffmpeg.org/
interface available at http://git.libav.org/
6. Checking source tree status:
......@@ -255,5 +255,5 @@ I. BASICS:
where $SHA1 is the commit SHA1 from the 'git log' output.
Contact the project admins <git at ffmpeg dot org> if you have technical
Contact the project admins <git at libav dot org> if you have technical
problems with the GIT server.
......@@ -20,7 +20,7 @@ libavfilter then check it out from the libavfilter repository into
some directory of your choice by:
@example
svn checkout svn://svn.ffmpeg.org/soc/libavfilter
svn checkout svn://svn.libav.org/soc/libavfilter
@end example
And then read the README file in the top directory to learn how to
......
......@@ -18,14 +18,14 @@ As many functions tend to be a bit difficult to understand because
of optimizations, it can be hard to optimize them further, or write
architecture-specific versions. It is recommended to look at older
revisions of the interesting files (web frontends for the various FFmpeg
branches are listed at http://ffmpeg.org/download.html).
branches are listed at http://libav.org/download.html).
Alternatively, look into the other architecture-specific versions in
the x86/, ppc/, alpha/ subdirectories. Even if you don't exactly
comprehend the instructions, it could help understanding the functions
and how they can be optimized.
NOTE: If you still don't understand some function, ask at our mailing list!!!
(http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-devel)
(https://lists.libav.org/mailman/listinfo/libav-devel)
When is an optimization justified?
......
......@@ -122,7 +122,7 @@ void ff_gmc_c(uint8_t *dst, uint8_t *src, int stride, int h, int ox, int oy,
/* minimum alignment rules ;)
If you notice errors in the align stuff, need more alignment for some ASM code
for some CPU or need to use a function with less aligned data then send a mail
to the ffmpeg-devel mailing list, ...
to the libav-devel mailing list, ...
!warning These alignments might not match reality, (missing attribute((align))
stuff somewhere possible).
......
......@@ -41,7 +41,7 @@
static const char* sample_message =
"Please file a bug report following the instructions at "
"http://ffmpeg.org/bugreports.html and include "
"http://libav.org/bugreports.html and include "
"a sample of this file.";
typedef struct SubStream {
......
......@@ -1204,8 +1204,8 @@ void av_log_ask_for_sample(void *avc, const char *msg)
if (msg)
av_log(avc, AV_LOG_WARNING, "%s ", msg);
av_log(avc, AV_LOG_WARNING, "If you want to help, upload a sample "
"of this file to ftp://upload.ffmpeg.org/MPlayer/incoming/ "
"and contact the ffmpeg-devel mailing list.\n");
"of this file to ftp://upload.libav.org/MPlayer/incoming/ "
"and contact the libav-devel mailing list.\n");
}
static AVHWAccel *first_hwaccel = NULL;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment