From: Tom Tromey <tromey@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: Wed, 13 Dec 2000 13:21:00 -0000 [thread overview]
Message-ID: <87ofyg3szi.fsf@creche.redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.30.0012071031150.50473-100000@deneb.dbai.tuwien.ac.at>
Gerald> ...can someone please give me write access to the GNATS CVS
Gerald> repository?
It looks like somebody already did.
Note that the sources/gcc.gnu.org gnatsweb is mildly hacked from the
official version. For instance it recognizes URL text in PR bodies
and turns it into a link when displaying. (I'd like to see this go in
to the official gnatsweb...)
Please tell me if you make significant changes. I'd like to keep the
gcc and sources gnatsweb copies more or less in sync.
Tom
next prev parent reply other threads:[~2000-12-13 13:21 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 ` gnatsweb Jeffrey A Law
2000-12-07 22:33 ` gnatsweb Paul Traina
2000-12-10 15:46 ` gnatsweb Gerald Pfeifer
2000-12-13 13:21 ` Tom Tromey [this message]
[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=87ofyg3szi.fsf@creche.redhat.com \
--to=tromey@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).