From: "Stuart Stevens" <stuart_stevens@sierralogic.com>
To: "'Chad Walstrom'" <chewie@wookimus.net>, <help-gnats@gnu.org>
Subject: RE: Responses to GNATS email
Date: Sun, 29 Aug 2004 02:27:00 -0000 [thread overview]
Message-ID: <E1C1AS6-0005c9-Dr@lists.gnu.org> (raw)
In-Reply-To: <20040828174241.GA30032@wookimus.net>
Chad
I found that the reply works for the "default" database, but not for other
databases. When I reply to a message from another database, a new PR is
created in the default database.
I created a test database and used it for testing. So the configuration is
the standard configuration.
Any ideas why it would create a new PR when the reply is using a different
database?
Thanks
Stuart
-----Original Message-----
From: Chad Walstrom [mailto:chewie@wookimus.net]
Sent: Saturday, August 28, 2004 10:43 AM
To: help-gnats@gnu.org
Cc: Stuart Stevens
Subject: Re: Responses to GNATS email
Stuart Stevens wrote:
> The default email configuration for GNATS email is to set the reply-to
> to "bugs" and have an email alias of bugs. When I reply to a GNAT
> email, a new PR is generated with the information in the reply.
This shouldn't happen if you retain the subject heading from the autoreply
GNATS sent you.
> I am using Red Hat Linux 8 with a fairly default sendmail/postfix
> configuration.
>
> What should happen when you reply to a GNAT generated email?
It should be appended to the current problem report in the Audit Trail.
> Would the new message be added to the existing GNAT?
Yep.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-08-28 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 17:45 Stuart Stevens
2004-08-28 21:04 ` Chad Walstrom
2004-08-29 2:27 ` Stuart Stevens [this message]
2004-08-31 14:34 ` Stuart Stevens
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=E1C1AS6-0005c9-Dr@lists.gnu.org \
--to=stuart_stevens@sierralogic.com \
--cc=chewie@wookimus.net \
--cc=help-gnats@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).