ceph/src/seastar/doc/contributing.md

   1 Contributing to Seastar
   2 =======================
   3
   4 # Sending Patches
   5 Seastar follows a patch submission similar to Linux. Send patches to seastar-dev, with a DCO signed off message. Use git send-email to send your patch.
   6
   7 Example:
   8
   9 1. When you commit, use "-s " in your git commit command, which adds a DCO signed off message. DCO is a "Developer's Certificate of Origin" http://elinux.org/Developer_Certificate_Of_Origin
  10
  11 For the commit message, you can prefix a tag for an area of the codebase the patch is addressing
  12
  13         git commit -s -m "core: some descriptive commit message"
  14
  15 2. then send an email to the google group
  16
  17         git send-email <revision>..<final_revision> --to seastar-dev@googlegroups.com
  18
  19 NOTE: for sending replies to patches, use --in-reply-to with the message ID of the original message. Also, if you are sending out a new version of the change, use git rebase and then a `git send-email` with a `-v2`, for instance, to denote that it is a second version.
  20
  21 # Testing and Approval
  22 Run test.py and ensure tests are passing (at least) as well as before the patch.
  23
  24
  25
  26
  27
  28
  29
  30