Re: networking bugs and bugme.osdl.org

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> If some low-value stuff leaks through then ho-hum, at least it was
> on-topic.  It is not as if we are unused to low-value content...

;-)
 
> It would be good if pure administrata such as changing the status were
> filtered.

That should be easy enough.
 
> In fact, there is probably no point in sending anything bugzilla->list apart
> from the initial report.  If the bug is then pursued via bugzilla then OK. 
> If is is pursued via email then bugzilla just captures the discussion.   

OK, but I'm pretty much doing that already. I try to filter out some of
the "bugs with no content". So it sounds like the issue is more the
loop from email back in. Will see what I can get done - have to schedule
some time from the admins.

>> 2. email back in.
>> 
>> Email back in is harder, and needs more thought as to how to make it
>> easy to use, whilst avoiding logging crap (eg. ensuing flamewars that 
>> derive from the bug reports, etc).
> 
> Well hopefully people will have the sense to cut the bugzilla address off
> the Cc line if it drifts off-topic.

Fairy nuff.
 
>> My intuition is to log replies by
>> default, and hack off certain threads by hand
> 
> Nah.  Just log everything and hack off the crap by larting people.

Heh. need to get a good "remote slap protocol" implemented. Perhaps
the net guys can write us an RFC for it ;-)

M.

-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux