public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Steve Kelem <kelem@adaptivesilicon.com>
To: Rick Macdonald <rickm@vsl.com>,
	gnats-devel <gnats-devel@sourceware.cygnus.com>
Subject: Re: How to add a field to the Gnats Data Base?
Date: Thu, 11 May 2000 11:06:00 -0000	[thread overview]
Message-ID: <391AF691.DD374079@adaptivesilicon.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10005110633130.21077-100000@sys4>

Thanks for your help!  There doesn't seem to be any documentation on the
release-based fields (like what type of values they take, and whether there
are any restrictions on the values). gnatsweb-2.7beta seems to know the fields
might be in the data base, but doesn't seem to do anything with them.

Steve

Rick Macdonald wrote:

> On Wed, 10 May 2000, Steve Kelem wrote:
>
> > How hard is it to add a field to the Gnats data base?
> > I need to add a field "By When?" that takes a date.
> > This will allow us to categorize each PR for when we intend to
> > fix/respond to them, and then concentrate on the PRs for a certain
> > release date.
>
> In GNATS 3.113, this already exists if you build it --with-release-based.
> The field is supported by TkGnats, I assume but don't know for sure that
> gnatsweb does as well, but you'll have to check.
>
> I think all you need to do after rebuilding gnats is to run "gen-index" to
> build a new index with the three new fields that you get
> --with-release-based. With TkGnats, you can "hide" the other two if you
> don't want them (Keywords and Quarter).
>
> In V4, you can add and subtract whatever you want!
>
> ...RickM...

  reply	other threads:[~2000-05-11 11:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-10 17:08 Steve Kelem
2000-05-11  5:43 ` Rick Macdonald
2000-05-11 11:06   ` Steve Kelem [this message]
2000-05-12  5:25     ` Rick Macdonald
2000-05-18 16:44       ` Steve Kelem
2000-05-19  6:05         ` Rick Macdonald

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=391AF691.DD374079@adaptivesilicon.com \
    --to=kelem@adaptivesilicon.com \
    --cc=gnats-devel@sourceware.cygnus.com \
    --cc=rickm@vsl.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).