User Tools

Site Tools


contributions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
contributions [2013/01/28 09:35]
rwlove [linux-scsi]
contributions [2015/02/05 14:15]
vasu [linux-scsi]
Line 14: Line 14:
  
  
-Open-FCoE was designed to be a Low Level Driver (LLD) of the Linux SCSI subsystem. We will discuss changes on fcoe-devel@open-fcoe.org,​ but all changes must be approved by the linux-scsi list and ultimately the Linux community before they are accepted into the kernel. ​Patches ​agreed upon by the Open-FCoE community will be collected ​and pushed to the linux-scsi mailing list at the appropriate times.+Open-FCoE was designed to be a Low Level Driver (LLD) of the Linux SCSI subsystem. We will discuss changes on fcoe-devel@open-fcoe.org,​ but all kernel code changes must be approved by the linux-scsi list and ultimately the Linux community before they are accepted into the kernel. ​FCoE user tools patches are finalized and applied at fcoe-devel@open-fcoe.org against its user tools git code repositories but kernel patches ​agreed upon by the Open-FCoE community will be collected ​by linux-scsi mailing list, so should be send directly linux-scsi while CCed to fcoe-devel@open-fcoe.org for their review and acceptance.
  
 ==== Reporting ==== ==== Reporting ====
Line 35: Line 35:
   - Please provide a "​Signed-off"​ line.   - Please provide a "​Signed-off"​ line.
   - Please prefix the title of your patch with something appropriate. For example, "​libfc:​ This patch fixes something"​. This allows us to easily keep track of patches for our code base and not the rest of the kernel. Investigate the 'git log' to see what other developers are using as prefixes.   - Please prefix the title of your patch with something appropriate. For example, "​libfc:​ This patch fixes something"​. This allows us to easily keep track of patches for our code base and not the rest of the kernel. Investigate the 'git log' to see what other developers are using as prefixes.
 +
 +
 +=== man Pages ===
 +
 +We use the '​a2x'​ command to convert an Asciidoc text file to both manpage format as well as other formats. If you are making changes to a man page please edit the corresponding .txt file in the doc/ directory. Next run '​make'​ which will run '​a2x'​ and generate the man page. Simply update your patch contribution with both the changes to the .txt file as well as the created .8 (man page) file. This process allows us to use the .txt file as the master document and all other formats are simply formatted versions of the original.
  
contributions.txt ยท Last modified: 2015/02/05 14:15 by vasu