Revision 87800dc2

View differences:

doc/TODO
69 69
- JPEG2000 decoder & encoder
70 70
- MPEG4 GMC encoding support
71 71
- macroblock based pixel format (better cache locality, somewhat complex, one paper claimed it faster for high res)
72
- regression tests for codecs which do not have an encoder (I+P-frame bitstream in svn)
72
- regression tests for codecs which do not have an encoder (I+P-frame bitstream in the 'master' branch)
73 73
- add support for using mplayers video filters to ffmpeg
74 74
- H264 encoder
75 75
- per MB ratecontrol (so VCD and such do work better)
doc/developer.texi
312 312
    If it depends on a parser or a library, did you add that dependency in
313 313
    configure?
314 314
@item
315
    Did you "svn add" the appropriate files before commiting?
315
    Did you "git add" the appropriate files before committing?
316 316
@end enumerate
317 317

  
318 318
@section patch submission checklist
......
325 325
@item
326 326
    Is the patch a unified diff?
327 327
@item
328
    Is the patch against latest FFmpeg SVN?
328
    Is the patch against latest FFmpeg git master branch?
329 329
@item
330 330
    Are you subscribed to ffmpeg-dev?
331 331
    (the list is subscribers only due to spam)
......
388 388
@section Patch review process
389 389

  
390 390
All patches posted to ffmpeg-devel will be reviewed, unless they contain a
391
clear note that the patch is not for SVN.
391
clear note that the patch is not for the git master branch.
392 392
Reviews and comments will be posted as replies to the patch on the
393 393
mailing list. The patch submitter then has to take care of every comment,
394 394
that can be by resubmitting a changed patch or by discussion. Resubmitted
doc/optimization.txt
17 17
As many functions tend to be a bit difficult to understand because
18 18
of optimizations, it can be hard to optimize them further, or write
19 19
architecture-specific versions. It is recommended to look at older
20
revisions of the interesting files (for a web frontend try ViewVC at
21
http://svn.ffmpeg.org/ffmpeg/trunk/).
20
revisions of the interesting files (web frontends for the various FFmpeg
21
branches are listed at http://ffmpeg.org/download.html).
22 22
Alternatively, look into the other architecture-specific versions in
23 23
the x86/, ppc/, alpha/ subdirectories. Even if you don't exactly
24 24
comprehend the instructions, it could help understanding the functions
doc/soc.txt
9 9
The Goal:
10 10
Our goal in respect to soc is and must be of course exactly one thing and
11 11
that is to improve FFmpeg, to reach this goal, code must
12
* conform to the svn policy and patch submission guidelines
12
* conform to the development policy and patch submission guidelines
13 13
* must improve FFmpeg somehow (faster, smaller, "better",
14 14
  more codecs supported, fewer bugs, cleaner, ...)
15 15

  
16 16
for mentors and other developers to help students to reach that goal it is
17 17
essential that changes to their codebase are publicly visible, clean and
18 18
easy reviewable that again leads us to:
19
* use of a revision control system like svn
19
* use of a revision control system like git
20 20
* separation of cosmetic from non-cosmetic changes (this is almost entirely
21 21
  ignored by mentors and students in soc 2006 which might lead to a suprise
22 22
  when the code will be reviewed at the end before a possible inclusion in

Also available in: Unified diff