Mercurial > mplayer.hg
diff DOCS/tech/svn-howto.txt @ 25395:0a40424a9d05
cosmetics: reformatting
author | diego |
---|---|
date | Sun, 16 Dec 2007 16:37:33 +0000 |
parents | b33844a43ca4 |
children | e4086b953952 |
line wrap: on
line diff
--- a/DOCS/tech/svn-howto.txt Sun Dec 16 16:29:25 2007 +0000 +++ b/DOCS/tech/svn-howto.txt Sun Dec 16 16:37:33 2007 +0000 @@ -244,18 +244,17 @@ keep related changes together. -4. Do not change behavior of the program (renaming options etc) or - remove functionality from the code without approval in a discussion on - the mplayer-dev-eng mailing list. +4. Do not change behavior of the program (renaming options etc) or remove + functionality from the code without approval in a discussion on the + mplayer-dev-eng mailing list. -5. Do not commit changes - 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 mplayer-dev-eng mailing - list, and if the code maintainers say OK, you may commit. This does not - apply to files you wrote and/or maintain. +5. Do not commit changes 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 mplayer-dev-eng + mailing list, and if the code maintainers say OK, you may commit. This does + not apply to files you wrote and/or maintain. 6. We refuse source indentation and other cosmetic changes if they are mixed @@ -276,11 +275,11 @@ 8. If you apply a patch by someone else, include the name and email address in - the log message. Since the mplayer-cvslog mailing list is publicly - archived you should add some spam protection to the email address. Send an - answer to mplayer-dev-eng (or wherever you got the patch from) saying that - you applied the patch. If the patch contains a documentation change, commit - that as well; do not leave it to the documentation maintainers. + the log message. Since the mplayer-cvslog mailing list is publicly archived + you should add some spam protection to the email address. Send an answer to + mplayer-dev-eng (or wherever you got the patch from) saying that you applied + the patch. If the patch contains a documentation change, commit that as + well; do not leave it to the documentation maintainers. 9. Do NOT commit to code actively maintained by others without permission. Send @@ -308,8 +307,8 @@ - use of internal or external libraries -13. Try to keep important discussions and requests (also) on the - mplayer-dev-eng mailing list, so that all developers can benefit from them. +13. Try to keep important discussions and requests (also) on the mplayer-dev-eng + mailing list, so that all developers can benefit from them. IRC is good for quick discussions, but nobody is there 24/7.