From: Petr Baudis <pasky@ucw.cz>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "David S. Miller" <davem@redhat.com>,
alan@lxorguk.ukuu.org.uk, greearb@candelatech.com,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: Re: networking bugs and bugme.osdl.org
Date: Sun, 20 Jul 2003 18:46:09 +0200 [thread overview]
Message-ID: <20030720164609.GH12132@pasky.ji.cz> (raw)
In-Reply-To: <17280000.1056940541@[10.10.2.4]>
Dear diary, on Mon, Jun 30, 2003 at 04:35:44AM CEST, I got a letter,
where "Martin J. Bligh" <mbligh@aracnet.com> told me, that...
> --"David S. Miller" <davem@redhat.com> wrote (on Sunday, June 29, 2003 15:13:02 -0700):
..snip..
> > The greatest tools in the world aren't useful if people don't want
> > to use them.
> >
> > Nobody wants to use tools unless it melds easily into their existing
> > daily routine. This means it must be email based and it must somehow
> > work via the existing mailing lists. It sounds a lot like what I'm
> > advocating except that there's some robot monitoring the list
> > postings.
>
> Agreed, the interface could be better - we're working on it. It won't
> be totally change free, but it could be better integrated. Feedback is
> very useful, though it helps a lot of you can pinpoint what's the
> underlying issue rather than "this is crap". Better email integration
> is top of the list, starting with sending stuff out to multiple people
> when filed, not a single bottleneck point.
Actually, it's not difficult to make Bugzilla to do things like sending out ALL
bugs updates emails to certain email adress(es), on a global basis or
per-module. Also, it is relatively easy to make Bugzilla _accept_ bugs updates
through email, from additional comments (+ attachments) to
status/priority/target/... changes.
It works quite nicely for us (ELinks) and it took just few hours to set up
properly (we had to touch the BZ sources, but just a little, the rest are
external support scripts). What is missing is some email interface for querying
the database (shouldn't be difficult to do, though), but if you just want to
file/update bugs, all you need is to:
* have the new bugs posted on the mailing list
* keep bugzilla in the cc list through the whole thread, as long as it's
relevant at least ;-)
* don't remove [Bug 12345] from the subject
If Martin would like some know-how about how to set things up, I could share
what we've done with him.
Kind regards,
--
Petr "Pasky" Baudis
.
Perfection is reached, not when there is no longer anything to add, but when
there is no longer anything to take away.
-- Antoine de Saint-Exupery
.
Stuff: http://pasky.ji.cz/
prev parent reply other threads:[~2003-07-20 16:46 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 5:30 networking bugs and bugme.osdl.org David S. Miller
2003-06-27 5:46 ` Martin J. Bligh
2003-06-27 5:47 ` David S. Miller
2003-06-27 7:59 ` Matti Aarnio
2003-06-27 8:00 ` David S. Miller
2003-06-27 15:00 ` Martin J. Bligh
2003-06-27 14:34 ` Martin J. Bligh
2003-06-27 14:56 ` Davide Libenzi
2003-06-27 21:37 ` David S. Miller
2003-06-27 21:54 ` Ben Greear
2003-06-27 21:54 ` David S. Miller
2003-06-27 22:15 ` Ben Greear
2003-06-27 22:19 ` David S. Miller
2003-06-27 22:36 ` Ben Greear
2003-06-28 0:00 ` David S. Miller
2003-06-28 0:15 ` Martin J. Bligh
2003-06-28 0:32 ` David S. Miller
2003-06-28 0:19 ` Larry McVoy
2003-06-28 0:27 ` Martin J. Bligh
2003-06-28 19:20 ` Alan Cox
2003-06-29 0:44 ` Martin J. Bligh
2003-06-27 23:08 ` Alan Cox
2003-06-28 0:21 ` David S. Miller
2003-06-28 19:19 ` Alan Cox
2003-06-28 22:03 ` David S. Miller
2003-06-28 23:15 ` Alan Cox
2003-06-28 23:20 ` David S. Miller
2003-06-28 23:46 ` Alan Cox
2003-07-12 17:07 ` Jan Rychter
2003-07-13 5:22 ` David S. Miller
2003-07-13 5:42 ` Jan Rychter
2003-06-27 23:12 ` Martin J. Bligh
2003-06-27 22:02 ` Davide Libenzi
2003-06-27 21:31 ` Ben Collins
2003-06-27 23:25 ` Andrew Morton
2003-06-27 22:30 ` Ben Collins
2003-06-28 0:32 ` Larry McVoy
2003-06-28 19:26 ` Alan Cox
2003-06-28 0:38 ` Martin J. Bligh
2003-06-28 1:14 ` Andrew Morton
2003-06-28 2:13 ` Martin J. Bligh
2003-06-28 2:35 ` Andrew Morton
2003-06-28 6:08 ` Martin J. Bligh
2003-06-28 3:27 ` Jamal Hadi
2003-06-27 22:02 ` David S. Miller
2003-06-27 22:11 ` Davide Libenzi
2003-06-27 22:13 ` David S. Miller
2003-06-27 18:50 ` Ben Greear
2003-06-27 21:44 ` David S. Miller
2003-06-27 22:47 ` Martin J. Bligh
2003-06-27 22:53 ` Larry McVoy
2003-06-28 0:44 ` David S. Miller
2003-06-28 0:09 ` David S. Miller
2003-06-27 23:04 ` Alan Cox
2003-06-28 0:19 ` David S. Miller
2003-06-29 21:15 ` David S. Miller
2003-06-29 21:45 ` Andries Brouwer
2003-06-29 21:51 ` David S. Miller
2003-06-29 22:49 ` Andries Brouwer
2003-06-29 23:21 ` Davide Libenzi
2003-06-29 22:07 ` Alan Cox
2003-06-29 22:13 ` David S. Miller
2003-06-30 2:35 ` Martin J. Bligh
2003-07-20 16:46 ` Petr Baudis [this message]
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=20030720164609.GH12132@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=netdev@oss.sgi.com \
/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).