blob: 5b6e6f7f3fefc44fb98e7fec61b5ab9069bc5513 [file] [log] [blame]
Harald Weltec271df72005-02-12 21:02:26 +00001A quick list of rules for committing stuff into netfilter svn:
Harald Welte710e7eb2003-04-13 11:29:28 +00002
Harald Weltec271df72005-02-12 21:02:26 +00003- Always include the Name of the Author/Contributor in the SVN comment
Harald Welte710e7eb2003-04-13 11:29:28 +00004 like 'fix for foo (Au Thor)'
5
6- make sure that you have set the executable bits on an 'extensions/.*-test'
Harald Weltec271df72005-02-12 21:02:26 +00007 script before adding/committing it to SVN
Harald Welte710e7eb2003-04-13 11:29:28 +00008
9- If the commit fixes a bugzilla bug, please include '(Closes: #bugnr)' in
10 the commit message
11
Harald Weltec271df72005-02-12 21:02:26 +000012- Make sure you don't commit to svn while a feature freeze is announced
Harald Welte710e7eb2003-04-13 11:29:28 +000013
14- For new extensions, there are two possible cases:
15 1) header files are just in patch-o-matic patch, you need an
16 'extensions/.*-test' script to have a conditional build
17 2) header files are in patch-o-matic patch, and copied to
18 'netfilter/include/linux/netfilter_xxx'. This way the extension
19 can be built _unconditionally_, and thus be included in
20 'extensions/Makefile'. Make sure to keep the headers in sync!
21
22 Usually '1)' is used, but in case something is expected to show up in the
23 kernel soon, we should already make userspace support unconditionally.
24