This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
howtocontribute [2015/04/19 00:34] smarx007 [Contributing Patches] Fix broken link to git book |
howtocontribute [2016/04/02 23:08] dcvmoole [Contributing Patches] we prefer GitHub pull requests! |
||
---|---|---|---|
Line 9: | Line 9: | ||
===== Contributing Patches ===== | ===== Contributing Patches ===== | ||
- | Patches are pieces of code that solve an existing issue. In fact, patches describe the changes between a before and after state. Patches will need to be created against the latest development version of [[http://git.minix3.org/?p=minix.git|MINIX3]] from Git and can be mailed to the [[http://groups.google.com/group/minix3|MINIX 3 Google Group]]. | + | Patches are pieces of code that solve an existing issue. In fact, patches describe the changes between a before and after state. Patches will need to be created against the latest development version of [[http://git.minix3.org/?p=minix.git|MINIX3 from Git]] (or from the official [[https://github.com/Stichting-MINIX-Research-Foundation/minix|mirror on GitHub]]). |
- | Also see DevelopersGuide/TrackingCurrent and [[http://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#Public-Project-over-E-Mail|Distributed Git - Contributing to a Project: Public Project over E-Mail]] | + | We prefer patches in the form of [[https://github.com/Stichting-MINIX-Research-Foundation/minix/pulls|pull requests on GitHub]]. If for some reason you are not able to create a GitHub pull request for your patch, you can send it to the [[http://groups.google.com/group/minix3|MINIX3 Google Group]] instead, but merging patches is a bit more work for us that way. |
+ | Also see the wiki page on [[DevelopersGuide:TrackingCurrent|tracking MINIX3-current]]. | ||
===== Contributing Packages ===== | ===== Contributing Packages ===== | ||