4 Some information about potential netsniff-ng hackers!
6 How to check out netsniff-ng?
7 =============================
9 git clone git://github.com/danborkmann/netsniff-ng.git
11 Some ideas of useful contributions/projects
12 ===========================================
14 The best way to propose your ideas is to outline them in a short mail to
15 workgroup@netsniff-ng.org or to our public mailing list address
16 netsniff-ng@googlegroups.com. We are looking forward for your proposals!
17 Of course, keep in mind that you can mail smaller fixes immediately.
19 How to make code contributions
20 ==============================
22 The best way to make a contribution to netsniff-ng is to send us your
23 code in the form of a unified diff against the latest released version
24 and, preferably, the version from Git.
25 Your patch should then be sent to bugs@netsniff-ng.org .
27 To make a unified diff, please follow these instructions:
29 1. Remove temporary files:
32 2. Rename your source tree:
34 mv netsniff-ng-xxx netsniff-ng-xxx-snazzy-feature
36 3. Checkout the original netsniff-ng source alongside it:
37 git clone git://github.com/danborkmann/netsniff-ng.git
39 4. Generate the diffs:
40 diff -urNb netsniff-ng-xxx netsniff-ng-xxx-snazzy-feature > /tmp/cool.patch
42 5. Check the patch and remove any unnecessary patches from the file.
44 6. If you've added several features, it's best to send them as
45 several independent patches if you can.
47 If you have just patched one or two files, then making patches is even
48 easier. For each file, just do:
51 [Make changes to file.c ...]
52 diff -u file.c.orig file.c > /tmp/file.c.patch
54 and just send us the patch: /tmp/file.c.patch.
59 Before submitting your patch make sure to indent your code appropriate.
65 The idea of the outline and some general parts for this HACKING file
66 derives from GNet (http://www.gnetlibrary.org/). Generally, I followed
67 the general structure of their HACKING file.