From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: Stephen Hemminger <shemminger@linux-foundation.org>,
bridge@linux-foundation.org
Cc: netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] bridge-utils 1.4
Date: Wed, 9 Jan 2008 08:40:35 +0200 [thread overview]
Message-ID: <20080109063654.M87339@visp.net.lb> (raw)
In-Reply-To: <20080108085607.37ab168f@deepthought>
As mentioned in
http://marc.info/?l=linux-bridge&m=113105949718826&w=2
Released package doesn't contain ./configure script
For people who know what is make on, it is easy to run autoconf , but some
know only how to use ./configure :-)
Other than this, it is works fine with me, but i didn't test it deeply yet.
On Tue, 8 Jan 2008 08:56:07 -0800, Stephen Hemminger wrote
> Minor update to bridge-utils. Mostly fixing bugs in usage of sysfs.
>
> Release tarball:
> http://downloads.sourceforge.net/bridge/bridge-utils-1.4.tar.gz
>
> Alon Bar-Lev (1):
> Allow bridge-utils to run when no TCP/IP is available
>
> Denys Vlasenko (1):
> fix use of sysfs (affects 32/64 bit compat)
>
> Jeremy Jackson (1):
> Fix parsing of port_id's (hex).
>
> Stephen Hemminger (3):
> Add ignore for generated files.
> Update gitignore
> Use linux/if.h rather than net/if.h
>
> --
> Stephen Hemminger <stephen.hemminger@vyatta.com>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2008-01-09 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:56 [ANNOUNCE] bridge-utils 1.4 Stephen Hemminger
2008-01-09 6:40 ` Denys Fedoryshchenko [this message]
2008-01-09 18:16 ` [Bridge] " Alon Bar-Lev
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=20080109063654.M87339@visp.net.lb \
--to=denys@visp.net.lb \
--cc=bridge@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).