From: Lars Henriksen <Lars.Henriksen@netman.dk>
To: Dirk Bergstrom <dirk@juniper.net>
Cc: Paul Traina <pst@juniper.net>, help-gnats@gnu.org
Subject: Re: X-GNATS-NOTIFY & the CC list in 4.0
Date: Tue, 21 May 2002 01:55:00 -0000 [thread overview]
Message-ID: <20020521082323.GB1262494@cluster2.netman.dk> (raw)
In-Reply-To: <C53744A44FBC9B4BAE90EB41D2C09AC2052264@proton.jnpr.net>
On Sat, Dec 22, 2001 at 02:44:26PM -0800, Dirk Bergstrom wrote:
> 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?
Sorry for the slow reaction. This is a good idea. I have noticed that you (?)
have removed X-GNATS-Notify from gnatsweb.pl in the current CVS version. I have
tested your suggestion of introducing a new field in dbconfig and it works out
fine.
One suggestion though. Instead of tagging a Cc: header onto Subject:, I have
simply added the new field (Notify-List in my case) to to-addresses in the
audit-mail format:
to-addresses {
"Notify-List"
"Responsible"
"$OldResponsible"
"Category[notify]"
"Submitter-Id[contact]"
"$EditUserEmailAddr"
"Reply-To:" | "From:" | "From"
}
By the way, there are still two X-GNATS-Notify occurrences left in gnatsweb.pl,
so the mail header is still present in PRs. Is that on purpose?
Lars Henriksen
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2002-05-21 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 19:29 Dirk Bergstrom
2001-11-20 17:52 ` Milan Zamazal
2001-12-23 14:13 ` Milan Zamazal
2001-12-22 14:45 ` Dirk Bergstrom
2002-05-21 1:55 ` Lars Henriksen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-17 9:43 Dirk Bergstrom
2001-11-17 12:27 ` Paul Traina
2001-12-22 8:16 ` Paul Traina
2001-12-21 19:13 ` Dirk Bergstrom
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=20020521082323.GB1262494@cluster2.netman.dk \
--to=lars.henriksen@netman.dk \
--cc=dirk@juniper.net \
--cc=help-gnats@gnu.org \
--cc=pst@juniper.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).