badzy.blogg.se - Vlcmedia

There will also be a post to the vlc-commits list ( subscribe here). If the patch gets approved, then there will normally be a post to the vlc-devel list to say "patch applied". You can check if your patch was received by the list at the list archive.

Try to avoid sending patches bigger than 100kB on the mailing list, if you can. You will be able to unsubscribe later easily if needed. Please subscribe to it before sending your patch otherwise, it may not get through the list's spam filters. Now you can send it to the vlc-devel mailing list.

Read your patch one more time using git show, and check that it looks OK.

Smith", "johnnykool1234", "J.S." or any other permutation.

For example, if you are John Smith with an e-mail of you should set your "Git name" to John Smith - real full name - not "jsmith", "John S", "J.

That is, that you are using your fullname, which is correctly capitalized and so on.

As a necessary exception, tabs are allowed within Makefiles.

pot files do not belong within source code patches. No unrelated changes are included in the patch.Indentation is correct, no tabs are introduced.No trailing spaces are introduced ( git show -color show them in red).`make distcheck` runs succesfully to the end. If the patch adds, removes or moves one or more files, make sure the distribution still works, i.e.If so, explain it in the patch description. In some rare cases, warnings are unavoidable or counter-productive to fix.The compiler does not mention new compilation warnings.Testing all combinations is impossible.Proper copyright license exists, and is stated where appropraite.As a special exception, language translations go to the last bugfix branch directly.Do not submit patches against releases.

Do not submit patches against a bugfix branch, except to backport fixes already found on the master branch.The patch applies to the latest master branch.The code mostly complies with the Code Conventions.This could be the second paragraph of your commit log. A more exhaustive explanation is also welcomed along with your patch.You should include a description that will be the commit log message of your patch.The patch email's subject should be prefixed by " ".Produce a patch according to the Git page, but don't send it yet.Get a modern Git version, 1.7 or higher.