From: Phil Edwards <pedwards@disaster.jaj.com>
To: Milan Zamazal <pdm@zamazal.org>
Cc: gnats-devel@sources.redhat.com
Subject: Re: disallowing intial high-priority PRs
Date: Mon, 25 Jun 2001 09:17:00 -0000 [thread overview]
Message-ID: <20010625110105.C30518@disaster.jaj.com> (raw)
In-Reply-To: <87zoaxyjsd.fsf@blackbird.zamazal.org>
On Sun, Jun 24, 2001 at 05:33:38PM +0200, Milan Zamazal wrote:
> - It's not worth to bother with GNATS 3.113, it's not developed anymore.
> The current development tree is GNATS 4 in CVS. It's a major rewrite
> so it's usually not possible to apply GNATS 3.113 patches into GNATS 4.
> See http://sources.redhat.com/gnats/ for information how to access
> GNATS' CVS.
>
> - The feature mustn't be hard-wired. Your improvement is useful to you
> and I'm sure it would be useful to other people as well, but not to
> everyone. If you think about such an improvement, I'd start with
> thinking about an appropriate configuration option in `dbconfig'
> (present only in GNATS 4).
Well, I hadn't really intended for this patch to go into the GNATS master
tree; really I just wanted opinions on whether the patch should do what I
want it to do. My thought was just to apply it to our local gnatsd (thus,
the 3.113 source). It would probably not be a useful feature for other
projects, so I can't suggest that it go into the development of GNATS 4.
> or you can run gnatsd manually from
> a command line.
Ah, I might try that instead.
Thanks for your note!
Phil
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC
next prev parent reply other threads:[~2001-06-25 9:17 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 [this message]
2001-06-26 14:30 ` Milan Zamazal
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=20010625110105.C30518@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=gnats-devel@sources.redhat.com \
--cc=pdm@zamazal.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).