From: Jeffrey A Law <law@redhat.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: Paul Traina <pst@juniper.net>,
gnats-devel@sources.redhat.com, overseers@sources.redhat.com
Subject: Re: gnatsweb
Date: Thu, 07 Dec 2000 15:58:00 -0000 [thread overview]
Message-ID: <19125.976233566@upchuck> (raw)
In-Reply-To: <Pine.BSF.4.30.0012071031150.50473-100000@deneb.dbai.tuwien.ac.at>
In message < Pine.BSF.4.30.0012071031150.50473-100000@deneb.dbai.tuwien.ac.at >
you write:
> [ overseers@sources.redhat.com added because of the CVS write issue. ]
>
> On Wed, 6 Dec 2000, Paul Traina wrote:
> > You're more than welcome to join the gang of un-maintainers if Ken
> > doesn't respond.
>
> Well, I got a mail bounce from his mail address, so...
>
> > Jason can set you up with access to the CVS repository.
>
> ...can someone please give me write access to the GNATS CVS repository?
Done.
jeff
next prev parent reply other threads:[~2000-12-07 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 16:22 gnatsweb Gerald Pfeifer
2000-12-06 18:57 ` gnatsweb Paul Traina
2000-12-07 1:34 ` gnatsweb Gerald Pfeifer
2000-12-07 15:58 ` Jeffrey A Law [this message]
2000-12-07 22:33 ` gnatsweb Paul Traina
2000-12-10 15:46 ` gnatsweb Gerald Pfeifer
2000-12-13 13:21 ` gnatsweb Tom Tromey
[not found] <pfeifer@dbai.tuwien.ac.at>
2000-12-08 8:17 ` gnatsweb Steffen Opel
2000-12-09 17:25 ` gnatsweb Paul Traina
2001-05-27 2:07 Gnatsweb James Dennis
2001-05-27 2:25 ` Gnatsweb Mark D. Baushke
2001-05-27 2:35 ` Gnatsweb James Dennis
2001-05-29 0:11 modular database backends Dirk Bergstrom
2001-07-09 1:10 ` gnatsweb Margaret BRIERTON
2001-07-09 1:29 ` gnatsweb S Ramesh
2003-08-08 17:38 GNATSWEB Hemant Wadhavankar
[not found] <20040804160052.588B6E486@mailfilter.gointernet.co.uk>
2004-08-05 16:03 ` GnatsWeb Adam Cade
2004-08-11 15:54 ` GnatsWeb James Eric Lawson
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=19125.976233566@upchuck \
--to=law@redhat.com \
--cc=gnats-devel@sources.redhat.com \
--cc=overseers@sources.redhat.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--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).