[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: X-GNATS-NOTIFY & the CC list in 4.0
From: |
Dirk Bergstrom |
Subject: |
RE: X-GNATS-NOTIFY & the CC list in 4.0 |
Date: |
Sat, 22 Dec 2001 14:44:26 -0800 |
> I seem to recall that they were deprecated in the 3.X
> timeframe because they
> never quite worked right, and we didn't have a great desire
> to fix them for 4.0.
ahh, that's what i'd suspected. if only i could remember *where* i came across
the idea...
> That said, what are you trying to do? There may be other
> better ways to skin this cat.
i was trying to figure out why the "CC these people on PR status email:" field
in gnatsweb didn't work. the answer is "because it's not connected to anything
on the back end".
so now the question becomes "should we yank this pseudo-field out of gnatsweb,
or add code to gnats?" my preference would be to whack it out of gnatsweb --
it's a hell of a lot simpler to *remove* code w/o creating bugs than it is to
add it.
i propose:
*) in place of x-gnats-notify, add a field to the standard dbconfig called
"CC-On-Change-List" (or something like that).
*) change the audit-mail format thusly:
header {
- format "Subject: Re: %s/%s\n"
+ format "Subject: Re: %s/%s\nCc: %s\n"
- fields { "Category" "Number" }
+ fields { "Category" "Number" "CC-On-Change-List" }
}
*) remove the Cc: and X-GNATS-Notify headers from send-pr, and remove the
[-c|--cc] option.
*) remove the code supporting XGN/CC from gnatsweb.
this will give us most of the same functionality, without a bunch of
bag-on-the-side support for random headers. it also gives users the choice of
whether or not to have a CC functionality.
what do y'all think?
--
Dirk Bergstrom address@hidden
_____________________________________________
Juniper Networks Inc., Computer Geek
Tel: 707.433.0564 Fax: 707.433.0769