You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

52 lines
1.4 KiB

  1. /** @page patchguide Patch Policies
  2. Please mail patches to:
  3. openocd-development@lists.berlios.de
  4. Note that you can't send patches to that list unless
  5. you're a member, despite what the list info page says.
  6. The patch should be against svn trunk using an SVN
  7. diff. If you use git-svn, a git diff or patch is OK
  8. too; likewise a quilt patch, if you use quilt.
  9. It should be a "good patch": focus it on a single
  10. issue, and make it be easily reviewable. Don't make
  11. it so large that it's hard to review; split large
  12. patches into smaller ones. (That can also help
  13. track down bugs later on.) All patches should
  14. be "clean", which includes preserving the existing
  15. coding style and updating documentation as needed.j
  16. Attach the patch to the email as a .txt file and
  17. also write a short change log entry that maintainers
  18. can copy and paste into the commit message
  19. Say if it's a bugfix (describe the bug) or a new
  20. feature. Don't expect patches to merge immediately
  21. for the next release. Be ready to rework patches
  22. in response to feedback.
  23. Add yourself to the GPL copyright for non-trivial changes.
  24. To create a patch from the command line:
  25. svn diff >mypatch.txt
  26. See:
  27. http://svnbook.red-bean.com/en/1.0/re09.html
  28. NB! remember to use "svn add" on new files first!
  29. http://svnbook.red-bean.com/en/1.0/re01.html
  30. If you have a decent SVN GUI, then that should be
  31. able to create and apply patches as well...
  32. */
  33. /** @file
  34. This file contains the @ref patchguide page.
  35. */