From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Stephen Hemminger <shemminger@osdl.org>, netdev@oss.sgi.com
Subject: Re: Iproute2: update
Date: Mon, 17 Jan 2005 23:24:37 +0100 [thread overview]
Message-ID: <20050117222437.GI26856@postel.suug.ch> (raw)
In-Reply-To: <1105997946.1078.308.camel@jzny.localdomain>
* jamal <1105997946.1078.308.camel@jzny.localdomain> 2005-01-17 16:39
> On Mon, 2005-01-17 at 15:57, Thomas Graf wrote:
> > > I'll put this changes into my tree given you're fine with it and stephen
> > > can pull them. As I said, the ipt code is still missing, I can merge
> > > them into my tree as well if you want.
> >
> > Stephen: you can pull jamal's changes with my modifications from
> > bk://tgr.bkbits.net/iproute2-tgr if you like.
>
> Thomas,
>
> Look at iproute2-2.6.10-ss050112 - ipt is in there and thats where my
> patches are against.
>
> ----
> [hadi@jzny hadi]$ find iproute2-2.6.10-ss050112 | grep ipt
> iproute2-2.6.10-ss050112/examples/dhcp-client-script
> iproute2-2.6.10-ss050112/tc/m_ipt.c
> iproute2-2.6.10-ss050112/ip/iptunnel.c
> iproute2-2.6.10-ss050112/include/iptables.h
> iproute2-2.6.10-ss050112/include/libiptc
> iproute2-2.6.10-ss050112/include/libiptc/ipt_kernel_headers.h
> iproute2-2.6.10-ss050112/include/libiptc/libip6tc.h
> iproute2-2.6.10-ss050112/include/libiptc/libiptc.h
> iproute2-2.6.10-ss050112/include/iptables_common.h
> iproute2-2.6.10-ss050112/include/linux/tc_act/tc_ipt.h
> -----------
Ah, great. I didn't look at the release and they're not in the
bk tree. Maybe stephen forgot to push his changes.
> So the IPT thing is unneeded. Also note that i had it the way you
> have it in configure but Stephen didnt like it.
OK. I don't care, it's really ugly to compile iproute2 without
iptables sources though.
> In regards to pedit - wait until the code goes in then shoot at it.
> Theres plenty of things for you to shoot at ;-> i think last time i
> really looked at it was ~2 years ago.
I'll keep those changes and eventually merge them sometimes. It's not
that important.
next prev parent reply other threads:[~2005-01-17 22:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 20:59 Iproute2: update Stephen Hemminger
2005-01-16 17:09 ` jamal
2005-01-16 17:45 ` Jamal Hadi Salim
2005-01-17 19:39 ` Thomas Graf
2005-01-17 20:20 ` Thomas Graf
2005-01-17 20:57 ` Thomas Graf
2005-01-17 21:39 ` jamal
2005-01-17 22:24 ` Thomas Graf [this message]
2005-01-17 22:39 ` jamal
2005-01-17 22:24 ` Stephen Hemminger
2005-03-21 20:11 ` Lennert Buytenhek
2005-03-29 18:09 ` Stephen Hemminger
2005-03-29 19:07 ` Lennert Buytenhek
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 18:17 iproute2 update Stephen Hemminger
2006-12-05 18:43 ` Patrick McHardy
2006-12-06 3:58 ` Masahide NAKAMURA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050117222437.GI26856@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).