ion
to be useful.
> This would probably involve giving Don Armstrong an account on a gnu.org
> machine that allows him to administer the debbugs server. Is this
> feasible?
The way we've done this in Debian is to have a debbugs user which all
of the debbugs stuff runs as, and sepa
ssassin? TMDA?
I suppose however you normally do it on the bugs-gnu-emacs mailing
list would be good. [The problem with me doing it on mail that doesn't
come to me directly is that it triggers some of the ham rules because
it comes from gnu.org.]
Don Armstrong
--
You could say she lived on t
t's not always
going to be that machine.]
> It's not terribly serious if a few messages go straight to the
> mailing-list without being fed through
> [EMAIL PROTECTED]
Right. And in any event, debbugs does have reasonable loop handling,
so most of these should be detected and dis
nts made line-length 82 columns ;-).
I can tweak things at my end if necessary to make sure that everything
either gets handled by submit or gets shot to the mailing list.
If this is ok with everyone, it'd be nice to give me a heads up before
deploying it though, so I'm around and can respond to any problems
that crop up. [I'm likely to be out for parts of this weekend.]
Don Armstrong
--
Build a fire for a man, an he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life.
-- Jules Bean
http://www.donarmstrong.com http://rzlab.ucr.edu
[EMAIL PROTECTED] instead.
It'd also be ok to send things with Bug#XXX headers not comming from
emacsbugs.donarmstrong.com to [EMAIL PROTECTED] [I
have to admit I'm rather more familiar with doing complicated things
in smartlist than mailman, where it's just a matter of tweaking a
. [I can give you the procmail rules
we use for [EMAIL PROTECTED] if it helps, though
they're pretty basic.]
[Once we're past the initial testing phases, I assume we'll move the
bug tracking system to a machine somewhere at gnu.org.]
Don Armstrong
--
"The trouble with you
