public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm at polyomino dot org dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/15977] Ada contributors should be documented
Date: Wed, 23 Jun 2004 15:08:00 -0000	[thread overview]
Message-ID: <20040623145550.28643.qmail@sourceware.org> (raw)
In-Reply-To: <20040613164541.15977.jsm28@gcc.gnu.org>


------- Additional Comments From jsm at polyomino dot org dot uk  2004-06-23 14:55 -------
Subject: Re:  Ada contributors should be documented

On Tue, 22 Jun 2004, charlet at gcc dot gnu dot org wrote:

> Any volunteer to e.g. write a script to extract the names ?

Extract them from where?  gcc/ada/ChangeLog only starts in 2001, and as
GNU Ada has existed for many years I suppose there are significant
contributors who haven't contributed since before then.  In any case,
someone needs to write descriptions of the contributions on the same sort
of level as the existing ones in contrib.texi.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15977


  parent reply	other threads:[~2004-06-23 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 16:45 [Bug ada/15977] New: " jsm28 at gcc dot gnu dot org
2004-06-13 17:56 ` [Bug ada/15977] " pinskia at gcc dot gnu dot org
2004-06-22 12:50 ` charlet at gcc dot gnu dot org
2004-06-23 15:08 ` jsm at polyomino dot org dot uk [this message]
2004-06-23 15:13   ` Arnaud Charlet
2004-06-23 15:18 ` charlet at act-europe dot fr
2004-08-13 20:30 ` jsm28 at gcc dot gnu dot org
2004-08-14 11:28 ` charlet at act-europe dot fr
2005-02-13 15:40 ` pinskia at gcc dot gnu dot org
2005-02-25  1:56 ` bosch at gcc dot gnu dot org
2005-02-28 22:38 ` cvs-commit at gcc dot gnu dot org
2005-02-28 23:02 ` bosch at gcc dot gnu dot org
2005-04-17 11:38 ` cvs-commit at gcc dot gnu dot org
2005-04-17 14:36 ` pinskia at gcc dot gnu dot org

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=20040623145550.28643.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).