From: Stephen Hemminger <shemminger@linux-foundation.org>
To: netdev@vger.kernel.org
Subject: Bugzilla: open bug reports
Date: Thu, 4 Oct 2007 09:44:26 -0700 [thread overview]
Message-ID: <20071004094426.5321af0e@freepuppy.rosehill> (raw)
Bugzilla report of open bugs. Yes you could run it yourself but
many of these bugs seem to be old and need some attention or work
to get resolved.
Would this be useful to regularly run/automate?
What format?
next reply other threads:[~2007-10-04 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 16:44 Stephen Hemminger [this message]
2007-10-04 16:45 ` [BUGZILLA] network device bugs Stephen Hemminger
2007-10-04 16:46 ` [BUGZILLA] network wireless bugs Stephen Hemminger
2007-10-04 16:47 ` [BUGZILLA] network bugs Stephen Hemminger
2007-10-04 16:55 ` Avinash Ramanath
2007-10-04 16:57 ` Stephen Hemminger
2007-10-04 17:35 ` Bugzilla: open bug reports Chuck Ebbert
2007-10-05 8:28 ` Steffen Klassert
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=20071004094426.5321af0e@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=netdev@vger.kernel.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