Re: [tcpdump-workers] -i man

2009-07-21 Thread Doru Georgescu
Guy Harris alum.mit.edu> writes: > I'd file the libpcap bug about the filter man page first, and then > close the tcpdump one about the expression section of the tcpdump man > page as a duplicate of the new libpcap bug. If, when you close a bug > as a duplicate, you can't specify the bug i

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-18 Thread Doru Georgescu
Guy Harris alum.mit.edu> writes: > SourceForge said comments were closed when they really meant "you have > to be logged in to make comments"? That's *REALLY* stupid, but error > reporting always seems to be one of the worst parts of software - > people want to work on the parts of the cod

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Guy Harris
On Jul 16, 2009, at 12:49 PM, Doru Georgescu wrote: Indeed, I was not logged in. I don't know how to apologize. By telling the SourceForge people that their error message is very unhelpful. :-) I.e., given how horribly wrong their error message is, I don't think you have anything for wh

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Doru Georgescu
> SourceForge said comments were closed when they really meant "you have > to be logged in to make comments"? That's *REALLY* stupid, but error > reporting always seems to be one of the worst parts of software - > people want to work on the parts of the code where things work, and > handli

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Doru Georgescu
> No - that section of the manual refers to selecting an interface, not > to matching packets when filtering. > > As far as I can tell, "ties are broken by choosing the earliest match" > means "for some reason, we didn't just say that the first interface in > the list is used". > Thanks. I

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Guy Harris
On Jul 16, 2009, at 12:10 PM, Doru Georgescu wrote: Yes, the comments have been definitely disabled, for me. This is what I see there (http://sourceforge.net/tracker/?func=detail&aid=2813234&group_id=53066&atid=469573 ), on a wonderful yellow background: Comments have been closed for this a

[tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Doru Georgescu
Yes, the comments have been definitely disabled, for me. This is what I see there (http://sourceforge.net/tracker/?func=detail&aid=2813234&group_id=53066&atid=469573), on a wonderful yellow background: Comments have been closed for this artifact. Also, the list subscription instructions on h

Re: [tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Guy Harris
On Jul 16, 2009, at 9:04 AM, Doru Georgescu wrote: Please explain what this means, -i in manual: "Ties are broken by choosing the earliest match." Ties between what and what? Match, I suppose, is between the tcpdump expression and packets headers. No - that section of the manual refers to sel

[tcpdump-workers] -i man "Ties are broken by choosing the earliest match."

2009-07-16 Thread Doru Georgescu
Please explain what this means, -i in manual: "Ties are broken by choosing the earliest match." Ties between what and what? Match, I suppose, is between the tcpdump expression and packets headers. I answer here to guy_harris on http://sourceforge.net/tracker/?func=detail&aid=2813234&group_id=5306