From: Milan Zamazal <pdm@zamazal.org>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: gnats-devel@sources.redhat.com
Subject: Re: disallowing intial high-priority PRs
Date: Tue, 26 Jun 2001 14:30:00 -0000 [thread overview]
Message-ID: <87vglkqmqg.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <20010625110105.C30518@disaster.jaj.com>
>>>>> "PE" == Phil Edwards <pedwards@disaster.jaj.com> writes:
PE> It would probably not be a useful feature for other projects, so
PE> I can't suggest that it go into the development of GNATS 4.
Referring to the recent discussion about access rights, one might want
to have a flag allowing to set the `high' priority too. I can imagine
situations when this would be useful. But it would require much more
work to implement it.
Regards,
Milan Zamazal
--
SomeProgrammersLikeWritingLikeThis.However,IDontThinkThisFormOfCommunicationIs\
AGoodIdea.IApologizeToAllWhoCantReadMyTextsWrittenInAClassicStyle.
prev parent reply other threads:[~2001-06-26 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 11:18 Phil Edwards
2001-06-24 11:26 ` Milan Zamazal
2001-06-25 9:17 ` Phil Edwards
2001-06-26 14:30 ` Milan Zamazal [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=87vglkqmqg.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=gnats-devel@sources.redhat.com \
--cc=pedwards@disaster.jaj.com \
/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).