From: Andrew Cagney <cagney@cygnus.com>
To: jlarmour@redhat.com, Jim Kingdon <kingdon@redhat.com>
Cc: ac131313@cygnus.com, overseers@sourceware.cygnus.com
Subject: Re: A patch for toplevel Makefile.in
Date: Mon, 20 Mar 2000 15:31:00 -0000 [thread overview]
Message-ID: <UspfG1w60kM0829YoS@cygnus.com> (raw)
Message-ID: <20000320153100.5M9eWDfNlmsCdKEBJee7UbFINaN9rgEVi21XRIOUzXk@z> (raw)
In-Reply-To: <200003202111.QAA08994@devserv.devel.redhat.com>
Excerpts from mail: 20-Mar-100 Re: A patch for toplevel Ma.. Jim
Kingdon@redhat.com (524*)
> > Perhaps we should consider adding a src-patches@sourceware list?
> Speaking of which, can the relevant people (gdb maintainer(s),
> binutils maintainer, newlib maintainer, whoever) get together and pick
> a project leader(s) for the "src" project?
At present binutils' (1) Ian L.T. is the defacto maintainer for any
stuff in the src directory. I pleed for a cross post so that gdb people
at least know something has/is about to change. The GDB people are very
unlikely to try to veto any changes.
For what its worth I tabled a suggestion (to binutils) to add a
src/MAINTAINERS file that would explain top level maintainership issues.
> Right now people are sending me things like changes to the modules
> file, and that really should be a project issue rather than a
> sourceware issue.
> P.S. src-patches@sourceware sounds good to me. But I'm not sure who
> is supposed to decide these things the way things are now.
Could work. Would still need a standard place for people to look to
determine what the rules are.
enjoy,
Andrew
(1) Wonder if that quote is correct
next prev parent reply other threads:[~2000-03-20 15:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000310125542.A6624@valinux.com>
[not found] ` <38CD8CF3.CA81E01@cygnus.com>
2000-12-30 6:08 ` Jonathan Larmour
2000-03-20 12:56 ` Jonathan Larmour
2000-12-30 6:08 ` Jim Kingdon
2000-03-20 13:11 ` Jim Kingdon
2000-12-30 6:08 ` Frank Ch. Eigler
2000-03-20 14:35 ` Frank Ch. Eigler
2000-12-30 6:08 ` Andrew Cagney [this message]
2000-03-20 15:31 ` Andrew Cagney
2000-12-30 6:08 ` Jason Molenda
2000-03-20 18:38 ` Jason Molenda
2000-12-30 6:08 ` Jason Molenda
2000-03-20 18:43 ` Jason Molenda
2000-12-30 6:08 ` Andrew Cagney
2000-03-20 20:15 ` Andrew Cagney
2000-12-30 6:08 ` Ian Lance Taylor
2000-03-20 19:43 ` Ian Lance Taylor
2000-12-30 6:08 ` Jim Kingdon
2000-03-20 20:09 ` Jim Kingdon
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=UspfG1w60kM0829YoS@cygnus.com \
--to=cagney@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=jlarmour@redhat.com \
--cc=kingdon@redhat.com \
--cc=overseers@sourceware.cygnus.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).