From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: jimb@codesourcery.com (Jim Blandy),
deuling@de.ibm.com (Markus Deuling),
gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc] [1/6] Remove macro CALL_DUMMY_LOCATION
Date: Mon, 04 Jun 2007 14:59:00 -0000 [thread overview]
Message-ID: <200706041459.l54ExN9A022350@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070601010037.GA32182@them.org> from "Daniel Jacobowitz" at May 31, 2007 09:00:37 PM
Daniel Jacobowitz wrote:
> On Thu, May 31, 2007 at 02:43:08PM -0700, Jim Blandy wrote:
> > Sheesh. (I did search the archives, but apparently not well enough.)
> > Could we put Markus on the Write After Approval list, with a note
> > about this? Say:
>
> It should be about IBM in general, not about Markus; I would prefer
> not to list people without write access, and it's not specific to him.
I agree. This is not really a matter of GDB repository write access
or maintainership responsibility; what this is about is really the
conditions of IBM's copyright assignment agreement with the FSF.
If any clarification in that area is required, it should probably go into
the FSF's copyright list, not the GDB MAINTAINERS file ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-06-04 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 7:22 Markus Deuling
2007-05-30 21:12 ` Jim Blandy
2007-05-31 11:18 ` Markus Deuling
2007-05-31 17:24 ` Daniel Jacobowitz
2007-05-31 21:44 ` Jim Blandy
2007-06-01 1:00 ` Daniel Jacobowitz
2007-06-04 14:59 ` Ulrich Weigand [this message]
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=200706041459.l54ExN9A022350@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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