On May 18, 2005, at 4:33 PM, mcr wrote:
I will cut a new beta, with a full pullup from HEAD of libpcap on
May
23. How is that?
Sounds good (although, at this point, the x.9 branches and HEAD are
the same for libpcap and tcpdump except for a couple of things in the
"tests" directory and the
-BEGIN PGP SIGNED MESSAGE-
> "Hannes" == Hannes Gredler <[EMAIL PROTECTED]> writes:
Hannes> i have a support for 4 more juniper specific DLTs on the
Hannes> boilerplate plus support for another BGP SAFI - i'd be
Hannes> gratfule if we could delay the R1 release until end o
On Mon, May 16, 2005 at 11:20:20AM -0700, Guy Harris wrote:
| Gianluca Varenni wrote:
|
| >Is there any new plan for the release of libpcap 0.9?
|
| At this point, I don't have anything additional planned for tcpdump
| (other than perhaps grabbing some more capture files from the Ethereal
| Web
- Original Message -
From: "Guy Harris" <[EMAIL PROTECTED]>
To:
Sent: Monday, May 16, 2005 11:20 AM
Subject: Re: [tcpdump-workers] preperation for 3.9 branch
Gianluca Varenni wrote:
Is there any new plan for the release of libpcap 0.9?
At this point, I don't hav
Gianluca Varenni wrote:
Is there any new plan for the release of libpcap 0.9?
At this point, I don't have anything additional planned for tcpdump
(other than perhaps grabbing some more capture files from the Ethereal
Web site and from mail to the Ethereal list, and running tcpdump against
those
is" <[EMAIL PROTECTED]>;
Sent: Monday, April 25, 2005 10:21 AM
Subject: Re: [tcpdump-workers] preperation for 3.9 branch
-BEGIN PGP SIGNED MESSAGE-
"Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
Guy> When were you planning on doing the 0.9/3.9 rel
-BEGIN PGP SIGNED MESSAGE-
> "Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
Guy> When were you planning on doing the 0.9/3.9 release?
I had planned to issue another beta today or Tuesday, and if there
were no issues, do the release on Saturday. (May 1).
I am behind on email
Michael Richardson wrote:
I leave you to advise what and if code should be pulled up.
I.e., pulled up to the x.9 branches?
So do you want to handle any pulling up, or should the people checking
in code do so?
(In either case, people checking in libpcap and tcpdump changes should
note that the
David Young wrote:
Radiotap is designed to be a variable-length header. When you say that
gencode will handle it, you mean that it will skip based on the length
field to the end of the radiotap header? If so, that sounds great!
That's the goal. There are a number of places that need to be change
On Wed, Apr 06, 2005 at 08:03:08PM -0700, Guy Harris wrote:
> Michael Richardson wrote:
>
> >I would like to plan a 3.9 branch and release for April.
> >I would propose branching on April 10, with the release around April 25.
> >
> >How does that sound?
>
> It sounds reasonable.
>
> (It turns ou
> Speaking of radio headers for 802.11 and link[M:N], I'm not sure a
> filter that tests those is necessarily useful - should the link[M:N]
> filters just test the 802.11 header and payload, and skip radio headers
> for the Prism, AVS, and radiotap headers? That way the same link[M:N]
> filter
-BEGIN PGP SIGNED MESSAGE-
> "Guy" == Guy Harris <[EMAIL PROTECTED]> writes:
Guy> Michael Richardson wrote:
>> I would like to plan a 3.9 branch and release for April. I would
>> propose branching on April 10, with the release around April 25.
>> How does that sound?
Michael Richardson wrote:
I would like to plan a 3.9 branch and release for April.
I would propose branching on April 10, with the release around April 25.
How does that sound?
It sounds reasonable.
(It turns out I might be able to get gencode.c to handle radiotap -
*all* filter expressions other
Alex Narinsky wrote:
How can I test STAP if all G-machines have new PacketData with longer
fields?
The only one is old but Nir does not allow me to test STAP on this
computer?
Was this supposed to be sent somewhere other than tcpdump-workers? It
sounds as if you wanted to send it to a co-worker o
:31 AM
To: tcpdump-workers@lists.tcpdump.org
Subject: [tcpdump-workers] preperation for 3.9 branch
-BEGIN PGP SIGNED MESSAGE-
I would like to plan a 3.9 branch and release for April.
I would propose branching on April 10, with the release around April 25.
How does that sound?
TASKS
-BEGIN PGP SIGNED MESSAGE-
I would like to plan a 3.9 branch and release for April.
I would propose branching on April 10, with the release around April 25.
How does that sound?
TASKS:
a) make sure CREDITS are up to date
b) make sure ChangeLog is up to date
c) ver
16 matches
Mail list logo
