Guy Harris <g...@alum.mit.edu> wrote: >> Done. If that header isn't present, the USB probing code isn't built >>or called, so you don't get information about attached USB devices as >>the first items in the trace unless they happen for some other reason.
> I've cherry-picked that to the 1.6 branch. > BTW, I don't see a 4.6 branch for tcpdump; will that be created soon as > well? Should be there. Weird, it wasn't on bpf. Maybe cause it was down when I first made the branches. It is there now.... There should be a branch: tcpdump-4.6 libpcap-1.6 there should be tags: tcpdump-4.6.0 libpcap-1.6.0 tcpdump-4.6.0-bp libpcap-1.6.0-bp I could add "X-Y.Z" tags to libpcap to augment the "X_Y_Z" tags and the "X_Y.Z" tags that are a relic from using CVS which can't handle - and . in tag names (which seeps into brains). -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers