From: Jeff Bailey <jbailey@nisa.net>
To: Paul Traina <pst@juniper.net>, Jeff Bailey <jbailey@nisa.net>,
gnats-devel@sourceware.cygnus.com
Subject: Re: Maintainer?
Date: Mon, 10 Jul 2000 11:40:00 -0000 [thread overview]
Message-ID: <20000710114032.A23487@sparky.nisa.net> (raw)
In-Reply-To: <002501bfea9c$e117e2e0$fba8c73f@trianon>
On Mon, Jul 10, 2000 at 11:30:09AM -0700, Paul Traina wrote:
I'm starting some patches for gnatsd to provide information on the
structure of the database. The next set will be the ability to modify
the database structure through gnatsd.
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.
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.
> I can help. What are your changes?
>
> ----- Original Message -----
> From: "Jeff Bailey" <jbailey@nisa.net>
> To: <gnats-devel@sourceware.cygnus.com>
> Sent: Monday, July 10, 2000 10:21 AM
> Subject: Maintainer?
>
>
> > Who is the current maintainer of GNATS? I have some patches that I'm
> > preparing against the CVS, but I notice that there hasn't been a commit
> > in months.
> >
> > --
> > "It is easy to be blinded to the essential uselessness of computers by
> > the sense of accomplishment you get from getting them to work at all."
> > - Douglas Adams
> >
--
"It is easy to be blinded to the essential uselessness of computers by
the sense of accomplishment you get from getting them to work at all."
- Douglas Adams
next prev parent reply other threads:[~2000-07-10 11:40 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 ` Jeff Bailey [this message]
2000-07-10 12:01 ` Maintainer? Paul Traina
2000-07-10 12:07 ` Maintainer? Jeff Bailey
2000-07-10 12:35 ` Maintainer? Bob Manson
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=20000710114032.A23487@sparky.nisa.net \
--to=jbailey@nisa.net \
--cc=gnats-devel@sourceware.cygnus.com \
--cc=pst@juniper.net \
/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).