From: Nick Clifton <nickc@redhat.com>
To: Anil Paranjape <AnilP1@KPITCummins.com>
Cc: binutils@sources.redhat.com
Subject: Re: Q: Estimated date for 2.16 release ?
Date: Mon, 14 Feb 2005 23:20:00 -0000 [thread overview]
Message-ID: <4210D684.7050002@redhat.com> (raw)
In-Reply-To: <4A1BE23A7B777442B60F4B4916AE0F1304621453@sohm.kpit.com>
Hi Anil,
> We are very keen to become maintainers for H8/300 target in Binutils. I would be grateful if you could tell me ( or give a link) which describes maintainer responsibilities. We will do our best to fulfill them.
There is a lot of information about maintainership of GNU projects at
this site:
http://www.gnu.org/prep/maintain/
The good news however is that for binutils being a maintainer of a port
to a particular target is lot simpler. So instead take a look at this
file:
<binutils-sources>/binutils/MAINTAINERS
and in particular the section on maintainers.
So if you feel that you can work to improve the h8/300 port, review
changes by other people to h8/300 specific files, and watch for changes
to the generic code that adversely affects the h8/300 port then you are
suitable to be a maintainer fir the h8/300 port.
Cheers
Nick
next prev parent reply other threads:[~2005-02-14 16:38 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-14 19:19 Anil Paranjape
2005-02-14 23:20 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-01 13:42 Anil Paranjape
2005-02-16 12:11 Anil Paranjape
2005-02-16 15:49 ` Nick Clifton
2005-02-14 10:47 Anil Paranjape
2005-02-14 10:50 ` Miles Bader
2005-02-14 15:08 ` Nick Clifton
2005-02-14 16:17 ` Nick Clifton
2005-01-27 13:45 Tomer Levi
2005-01-27 14:00 ` Daniel Jacobowitz
2005-01-27 14:07 ` Christian Joensson
2005-01-27 14:12 ` Eric Botcazou
2005-01-27 14:34 ` Jakub Jelinek
2005-02-14 10:46 ` Eric Botcazou
2005-02-14 13:01 ` Eric Botcazou
2005-01-27 14:26 ` Joel Sherrill <joel@OARcorp.com>
2005-01-27 14:36 ` Hans-Peter Nilsson
2005-02-24 18:53 ` Daniel Jacobowitz
2005-02-24 19:03 ` Hans-Peter Nilsson
2005-02-24 19:09 ` Joel Sherrill <joel@OARcorp.com>
2005-02-24 20:36 ` Eric Norum
2005-01-27 14:27 ` Hans-Peter Nilsson
2005-01-27 15:12 ` Ian Lance Taylor
2005-01-27 15:56 ` Hans-Peter Nilsson
2005-01-27 16:06 ` Daniel Jacobowitz
2005-01-31 2:11 ` Hans-Peter Nilsson
2005-02-24 17:54 ` Daniel Jacobowitz
2005-01-27 18:45 ` Thorsten Glaser
2005-02-24 17:49 ` Daniel Jacobowitz
2005-02-24 18:17 ` Thorsten Glaser
2005-04-25 8:06 ` Thorsten Glaser
2005-01-27 19:09 ` The Doctor
2005-01-31 11:40 ` Nick Clifton
2005-01-31 0:25 ` Ben Elliston
2005-01-31 0:42 ` Daniel Jacobowitz
2005-01-31 1:01 ` Ben Elliston
2005-02-24 17:50 ` Daniel Jacobowitz
2005-01-31 0:30 ` Ben Elliston
2005-01-31 0:42 ` Daniel Jacobowitz
2005-01-31 17:15 ` Nick Clifton
2005-02-24 18:40 ` Daniel Jacobowitz
2005-03-08 20:53 ` Daniel Jacobowitz
2005-03-10 9:32 ` Nick Clifton
2005-03-21 11:00 ` Alan Modra
2005-03-21 11:52 ` Daniel Jacobowitz
2005-01-31 16:25 ` Nick Clifton
2005-02-14 18:07 ` Aaron W. LaFramboise
2005-02-15 17:10 ` Nick Clifton
2005-02-24 18:59 ` Daniel Jacobowitz
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=4210D684.7050002@redhat.com \
--to=nickc@redhat.com \
--cc=AnilP1@KPITCummins.com \
--cc=binutils@sources.redhat.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).