From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
pablo@netfilter.org
Subject: Re: Notification of new BZ entries
Date: Tue, 09 Jun 2009 13:01:55 +0200 [thread overview]
Message-ID: <4A2E4123.7030608@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0906082341230.3946@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Dear co-developers,
>
>
> the netfilter bugzilla currently by default still assigns new
> entries to laforge.
>
> Unfortunately this means there will be no notification to
> $current_developer_set, and entries be missed. I try to regularly sweep
> along to catch new entries, but sometimes I forget.
> Since the amount of new entries in BZ is really low, could not BZ be set
> up to throw a mail to nf-dev whenever a new item gets created?
We do have a bugzilla list for that already. The default should
be changed anyways of course, but I thought Pablo already did that?
next prev parent reply other threads:[~2009-06-09 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 21:44 Notification of new BZ entries Jan Engelhardt
2009-06-09 11:01 ` Patrick McHardy [this message]
2009-06-09 14:23 ` Pablo Neira Ayuso
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=4A2E4123.7030608@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).