| Message ID | 20230826180748.15977-5-anton@khirnov.net |
|---|---|
| State | Accepted |
| Commit | 4c4bf54d99a7245683aef6a197179043df8b178c |
| Headers | show |
| Series | [FFmpeg-devel,1/6] doc/developer: move a sentence to a more appropriate place | expand |
| Context | Check | Description |
|---|---|---|
| yinshiyou/make_loongarch64 | success | Make finished |
| yinshiyou/make_fate_loongarch64 | success | Make fate finished |
| andriy/make_x86 | success | Make finished |
| andriy/make_fate_x86 | success | Make fate finished |
Il sab 26 ago 2023, 20:08 Anton Khirnov <anton@khirnov.net> ha scritto: > 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. > --- > doc/developer.texi | 9 --------- > 1 file changed, 9 deletions(-) > Agree, lgtm. >
diff --git a/doc/developer.texi b/doc/developer.texi index afa0148137..e4ba263581 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. -@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