Next: Feature Requests, Previous: Coding Style, Up: Top [Contents][Index]
Ideally, the best way to get your patches into the SXEmacs code base is to have Steve fetch them directly from your git repo. If, for any reason you are not able to set up a repository with read-only access for (at least) Steve, that doesn’t mean that you can’t still contribute your patches and code.
You can check how to setup a publicly accessible repo at See Setting up a publicly accessible repo.
There are a number of different situations and circumstances that you may find yourself in with regards to contributing to the SXEmacs project. I’ll try to cover the main ones here, but please note that they all have two things in common…
diff -u oldfile newfile
• Sending a patch from a git repo: | Procedure to send a patch from a git repo, be it a publicly accessible one, or just a private clone from the master repo. | |
• Vanilla sources (no repo): | Just the source tree that isn’t under git control. |