[FFmpeg-cvslog] doc/developer: drop an outdated item

Anton Khirnov git at videolan.org
Tue Oct 3 17:03:26 EEST 2023

ffmpeg | branch: master | Anton Khirnov <anton at khirnov.net> | Thu Aug 24 10:46:46 2023 +0200| [4c4bf54d99a7245683aef6a197179043df8b178c] | committer: Anton Khirnov

doc/developer: drop an outdated item

It dates back to pre-2005 days, when people generally tended to commit
their work directly without going through the mailing list. Few
developers do it today, and never outside of their standalone modules.
This item is thus confusing and misleading and is better removed.

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=4c4bf54d99a7245683aef6a197179043df8b178c

 doc/developer.texi | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index b4aef256c0..6a67515980 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -365,15 +365,6 @@ later on.
 Also if you have doubts about splitting or not splitting, do not hesitate to
 ask/discuss it on the developer mailing list.
- at subheading Ask before you change the build system (configure, etc).
-Do not commit changes to the build system (Makefiles, configure script)
-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
-list, and if the code maintainers say OK, you may commit. This does not
-apply to files you wrote and/or maintain.
 @subheading Cosmetic changes should be kept in separate patches.
 We refuse source indentation and other cosmetic changes if they are mixed
 with functional changes, such commits will be rejected and removed. Every

More information about the ffmpeg-cvslog mailing list