diff options
| author | Daniel Borkmann <dborkman@redhat.com> | 2013-03-15 10:41:48 +0100 |
|---|---|---|
| committer | Daniel Borkmann <dborkman@redhat.com> | 2013-03-15 10:41:48 +0100 |
| commit | 1a9fbac03c684f29cff9ac44875bd9504a89f54e (patch) | |
| tree | 1b2e40dbe5dc1899ef5b62c4325c9b94c9c450fc /REPORTING-BUGS | |
all: import netsniff-ng 0.5.8-rc0 source
We decided to get rid of the old Git history and start a new one for
several reasons:
*) Allow / enforce only high-quality commits (which was not the case
for many commits in the history), have a policy that is more close
to the one from the Linux kernel. With high quality commits, we
mean code that is logically split into commits and commit messages
that are signed-off and have a proper subject and message body.
We do not allow automatic Github merges anymore, since they are
total bullshit. However, we will either cherry-pick your patches
or pull them manually.
*) The old archive was about ~27MB for no particular good reason.
This basically derived from the bad decision that also some PDF
files where stored there. From this moment onwards, no binary
objects are allowed to be stored in this repository anymore.
The old archive is not wiped away from the Internet. You will still
be able to find it, e.g. on git.cryptoism.org etc.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'REPORTING-BUGS')
| -rw-r--r-- | REPORTING-BUGS | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS new file mode 100644 index 0000000..6d10ce7 --- /dev/null +++ b/REPORTING-BUGS @@ -0,0 +1,18 @@ +For reporting bugs send an email to the <netsniff-ng@googlegroups.com> list. + +If you use Fedora or have a RHEL subscription, you can also report bugs to: + + * https://bugzilla.redhat.com/ + +If you use Debian Linux, we might also process / track bugs there: + + * http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=netsniff-ng + +In any way, you'll get a reply from us. Please do not contact individual +developers directly in case of netsniff-ng issues or patches, but rather +always our mailing list. By this, you're not wasting time of a single +developer and increase your chances of getting a reply from us. + +In general, we are also highly interested in how you use the toolkit, what +problems you are trying to sovle and what kind of things you would like to have +improved. So feel free to drop us some feature requests as well. |