diff options
| -rw-r--r-- | README | 6 | ||||
| -rw-r--r-- | README.aix | 2 | ||||
| -rw-r--r-- | pcap-int.h | 2 | ||||
| -rw-r--r-- | pcap/pcap.h | 2 | ||||
| -rw-r--r-- | pcap1.h | 2 |
5 files changed, 7 insertions, 7 deletions
@@ -15,7 +15,7 @@ Version 1.x.y of LIBPCAP can be retrieved with the CVS tag "libpcap_1_{x}rel{y}" Please submit patches by forking the branch on GitHub at - http://github.com/mcr/libpcap/tree/master + http://github.com/the-tcpdump-group/libpcap/tree/master and issuing a pull request. @@ -97,12 +97,12 @@ to the address "tcpdump-workers@lists.tcpdump.org". Bugs, support requests, and feature requests may also be submitted on the GitHub issue tracker for libpcap at - https://github.com/mcr/libpcap/issues + https://github.com/the-tcpdump-group/libpcap/issues Source code contributions, etc. should be sent to the email address above or submitted by forking the branch on GitHub at - http://github.com/mcr/libpcap/tree/master + http://github.com/the-tcpdump-group/libpcap/tree/master and issuing a pull request. @@ -22,7 +22,7 @@ Using BPF: If you fix the problems yourself, please submit a patch by forking the branch at - https://github.com/mcr/libpcap/issues + https://github.com/the-tcpdump-group/libpcap/issues and issuing a pull request, so we can incorporate the fixes into the next release. @@ -379,7 +379,7 @@ struct pcap_timeval { * * Then supply the changes by forking the branch at * - * https://github.com/mcr/libpcap/issues + * https://github.com/the-tcpdump-group/libpcap/issues * * and issuing a pull request, so that future versions of libpcap and * programs that use it (such as tcpdump) will be able to read your new diff --git a/pcap/pcap.h b/pcap/pcap.h index 7be36b17..d022cd34 100644 --- a/pcap/pcap.h +++ b/pcap/pcap.h @@ -115,7 +115,7 @@ typedef struct pcap_addr pcap_addr_t; * * Then supply the changes by forking the branch at * - * https://github.com/mcr/libpcap/issues + * https://github.com/the-tcpdump-group/libpcap/issues * * and issuing a pull request, so that future versions of libpcap and * programs that use it (such as tcpdump) will be able to read your new @@ -105,7 +105,7 @@ typedef struct pcap_addr pcap_addr_t; * * Then supply the changes by forking the branch at * - * https://github.com/mcr/libpcap/issues + * https://github.com/the-tcpdump-group/libpcap/issues * * and issuing a pull request, so that future versions of libpcap and * programs that use it (such as tcpdump) will be able to read your new |