On Mar 25, 2013, at 12:24 PM, Guy Harris <g...@alum.mit.edu> wrote:
> Should we make new libpcap_1.4 and tcpdump_4.4 branches from the trunk, so
> that they reflect what's in the rc3 tarballs?
OK, I've done that. Building release tarballs from those branches produces
release tarballs that are the same as the rc3 tarballs, except that
1) the libpcap CHANGES file from the libpcap_1.4 branch has an entry I
just added for the Bluetooth fixes;
2) the tcpdump CHANGES file from the tcpdump_4.4 branch has some
entries for the new print-msnlb.c, print-vxlan.c, and print-otv.c printers and
for changes to the BGP printer;
3) the tcpdump tests directory from the tcpdump_4.4 branch is missing
failure-outputs.txt and lmp.new.
The first is a change that should go into the final 1.4.0 tarball.
The second is a change that should go into the final 4.4.0 tarball.
The second might reflect files left over from running a test in the 4.4.0 tree
from which the rc3 tarball was made, so I assume those files are *not* supposed
to be in the final 4.4.0 tarball.
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
