[Ffmpeg-cvslog] r5458 - in trunk/doc: faq.texi ffmpeg-doc.texi ffmpeg_powerpc_performance_evaluation_howto.txt optimization.txt
Fri Jun 9 11:55:05 CEST 2006
Date: Fri Jun 9 11:55:04 2006
New Revision: 5458
CVS --> Subversion
--- trunk/doc/faq.texi (original)
+++ trunk/doc/faq.texi Fri Jun 9 11:55:04 2006
@@ -103,9 +103,9 @@
@section I have a problem with an old version of ffmpeg; where should I report it?
Nowhere. Upgrade to the latest release or if there is no recent release upgrade
-to CVS. You could also try to report it. Maybe you will get lucky and
+to Subversion HEAD. You could also try to report it. Maybe you will get lucky and
become the first person in history to get an answer different from "upgrade
+to Subversion HEAD".
@section -f jpeg doesn't work.
@@ -253,7 +253,7 @@
@section I have a file in memory / a API different from *open/*read/ libc how do i use it with libavformat ?
-You have to implement a URLProtocol, see libavformat/file.c in FFmpeg CVS
-and libmpdemux/demux_lavf.c in MPlayer CVS.
+You have to implement a URLProtocol, see libavformat/file.c in FFmpeg
+and libmpdemux/demux_lavf.c in MPlayer sources.
--- trunk/doc/ffmpeg-doc.texi (original)
+++ trunk/doc/ffmpeg-doc.texi Fri Jun 9 11:55:04 2006
@@ -1170,7 +1170,7 @@
The presentation is the one specified by 'indent -i4 -kr -nut'.
The TAB character is forbidden outside of Makefiles as is any
form of trailing whitespace. Commits containing either will be
-rejected by the CVS repository.
+rejected by the Subversion repository.
Main priority in FFmpeg is simplicity and small code size (=less
@@ -1213,8 +1213,8 @@
fprintf and printf are forbidden in libavformat and libavcodec,
please use av_log() instead.
- at node CVS Policy
- at section CVS Policy
+ at node Development Policy
+ at section Development Policy
@@ -1265,7 +1265,7 @@
particular bug. Comments such as "fixed!" or "Changed it." are unacceptable.
If you apply a patch by someone else, include the name and email address in
- the CVS log message. Since the ffmpeg-cvslog mailing list is publicly
+ the log message. Since the ffmpeg-cvslog 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
you applied the patch.
@@ -1273,7 +1273,7 @@
Do NOT commit to code actively maintained by others without permission. Send
a patch to ffmpeg-devel instead.
- Subscribe to the ffmpeg-cvslog mailing list. The diffs of all CVS commits
+ Subscribe to the ffmpeg-cvslog 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.
@@ -1282,14 +1282,6 @@
unsure how best to do this, send a patch to ffmpeg-devel, the documentation
maintainer(s) will review and commit your stuff.
- Revert a commit ONLY in case of a big blunder like committing something not
- intended to be committed or committing a wrong file, the wrong version of a
- patch, CVS policy violation or broken code and you are going to recommit the
- right thing immediately.
- Never revert changes made a long time ago or buggy code. Fix it in the
- normal way instead.
- at item
Never write to unallocated memory, never write over the end of arrays,
always check values read from some untrusted source before using them
as array index or other risky things.
@@ -1347,7 +1339,7 @@
@section Regression tests
-Before submitting a patch (or committing to CVS), you should at least
+Before submitting a patch (or committing to the repository), you should at least
test that you did not break anything.
The regression tests build a synthetic video stream and a synthetic
--- trunk/doc/ffmpeg_powerpc_performance_evaluation_howto.txt (original)
+++ trunk/doc/ffmpeg_powerpc_performance_evaluation_howto.txt Fri Jun 9 11:55:04 2006
@@ -43,10 +43,10 @@
usual, but add the "--powerpc-perf-enable" option. For instance:
-./configure --prefix=/usr/local/ffmpeg-cvs --cc=gcc-3.3 --tune=7450 --powerpc-perf-enable
+./configure --prefix=/usr/local/ffmpeg-svn --cc=gcc-3.3 --tune=7450 --powerpc-perf-enable
-This will configure FFmpeg to install inside /usr/local/ffmpeg-cvs,
+This will configure FFmpeg to install inside /usr/local/ffmpeg-svn,
compiling with gcc-3.3 (you should try to use this one or a newer
gcc), and tuning for the PowerPC 7450 (i.e. the newer G4; as a rule of
thumb, those at 550Mhz and more). It will also enable the PMC.
--- trunk/doc/optimization.txt (original)
+++ trunk/doc/optimization.txt Fri Jun 9 11:55:04 2006
@@ -13,8 +13,8 @@
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 recommened to look at older
-CVS versions of the interesting files (just use ViewCVS at
+revisions of the interesting files (for a web frontend try ViewVC at
Alternatively, look into the other architecture-specific versions in
the i386/, ppc/, alpha/ subdirectories. Even if you don't exactly
comprehend the instructions, it could help understanding the functions
More information about the ffmpeg-cvslog