From: Bob Manson <manson@juniper.net>
To: gnats-devel@sourceware.cygnus.com
Subject: Re: Maintainer?
Date: Mon, 10 Jul 2000 12:35:00 -0000 [thread overview]
Message-ID: <200007101938.MAA15190@tristam.juniper.net> (raw)
In-Reply-To: <20000710114032.A23487@sparky.nisa.net>
There hasn't been an checkins because there hasn't been any
development going on lately, nor any bug reports. The only thing
holding up the release is updating the info files; I haven't had time,
and nobody has volunteered...
>I'm starting some patches for gnatsd to provide information on the
>structure of the database.
Like what exactly?
> The next set will be the ability to modify
>the database structure through gnatsd.
Uuuggggghhh...are you sure this is a good idea?
I guess I don't have a problem with this, but it needs to be
well-structured (as opposed to simply adding the ability to send a new
copy of the dbconfig file to the server).
>I'm cooking up a front end for my work that looks a little bit more like
>bugzilla. It will be done in PHP. I may offer it for the contrib/
>directory.
That part sounds nice.
>I wanted to make sure that Gnats was still being maintained/it was
>possible to contribute, so I don't have to fork. I think I may already
>have assignment papers into the FSF from 3 or 4 years ago.
If you send in patches, they'll be reviewed and integrated.
Bob
prev parent reply other threads:[~2000-07-10 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 10:21 Maintainer? Jeff Bailey
2000-07-10 11:33 ` Maintainer? Paul Traina
2000-07-10 11:40 ` Maintainer? Jeff Bailey
2000-07-10 12:01 ` Maintainer? Paul Traina
2000-07-10 12:07 ` Maintainer? Jeff Bailey
2000-07-10 12:35 ` Bob Manson [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=200007101938.MAA15190@tristam.juniper.net \
--to=manson@juniper.net \
--cc=gnats-devel@sourceware.cygnus.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).