From: Rick Macdonald <rickm@vsl.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: gnats-devel@sourceware.cygnus.com
Subject: Re: Submitting PR's 'closed' or with predetermined closing time.
Date: Fri, 12 May 2000 06:40:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10005120724280.29066-100000@sys4> (raw)
In-Reply-To: <Pine.LNX.4.21.0005112145310.13629-100000@netcore.fi>
On Thu, 11 May 2000, Pekka Savola wrote:
> I think this feature might be useful in environments where many
> administrators file "for-inform" informational PR's in the database.
>
> Is it possible to file new PR's as 'closed'? At least Gnatsweb doesn't
> support this. The reason? Because this is informational (of which some
> are there for archival purposes only), it might not make sense having to
> remember to close the PR and thus sending excess messages to all
> concerning parties.
This was always mostly in the gnats core, I think, but 10 months ago I
fixed up a couple of details and we use it all the time with TkGnats for
exactly the same reason.
I _think_ gnatsweb would present the state field in the sendpr form by
simply setting the "show-in-send-pr-form-please" flag (don't have the name
handy), but there may be more to it that this.
> Another interesting feature might be a PR that would automatically close
> or change state without sending those informational emails. This way,
> some new announcement would show in open reports for a while, and after
> some time (when people have probably seen it), it would be silently
> archived.
I have a state of "purge", which has state class of "closed". I never
wrote the script yet, but the intention is to a have a script that deltes
from the gnats database all PRs with a state of purge that have been
closed longer than some number of days.
Built-in generic support for such features would be interesting, as you
say. Perhaps in V4 some day...
...RickM...
prev parent reply other threads:[~2000-05-12 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 11:54 Pekka Savola
2000-05-12 6:40 ` Rick Macdonald [this message]
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=Pine.GSO.4.10.10005120724280.29066-100000@sys4 \
--to=rickm@vsl.com \
--cc=gnats-devel@sourceware.cygnus.com \
--cc=pekkas@netcore.fi \
/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).