Difference between revisions of "Sending Patches VLC"
Jump to navigation
Jump to search
Pdherbemont (talk | contribs) |
Pdherbemont (talk | contribs) |
||
| Line 2: | Line 2: | ||
* Get the latest [[Git]] revision | * Get the latest [[Git]] revision | ||
* Make your changes and commit them | * Make your changes and commit them | ||
| − | * Produce a [[Patches|patch]] according to [[Git#Submitting_patches_to_the_vlc-devel|the git page]]. | + | * Produce a [[Patches|patch]] according to [[Git#Submitting_patches_to_the_vlc-devel|the git page]], '''don't send it yet''', read the following before sending. |
== Check List == | == Check List == | ||
Revision as of 12:10, 12 April 2008
Contents
How to produce a Patch
- Get the latest Git revision
- Make your changes and commit them
- Produce a patch according to the git page, don't send it yet, read the following before sending.
Check List
When you send a patch make sure that:
- it mostly complies to the Code Conventions
- Make sure that it does not add more failure to `make check`
- Make sure that your patch is produced against the latest trunk. (Most of the time patch are against branches version such as 0.8.6 series which is not a development version. If this is a bugfix it may be backported, but should go in trunk first.).
Sending it to the vlc-devel
Now you can send it to the vlc-devel. Please subscribe to it before sending your patch, or else it may not got through the list's spam filters. You will be able to unsuscribe later easily if needed.
Writing an appropriate description
- The patch email's subject should be prefixed by "[Patch]".
- You should include a description that will be the commit log message of your patch
- A more exhaustive explanation is also welcomed along with your patch.
Getting your patch merged
- Don't hesitate to ask for review if after a week there is no replies.
- If there are comments, please answer to those and eventually correct your patch if possible.
That should ensure that your patch gets merged.
