From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
Date: Thu, 22 Nov 2001 13:53:00 -0000 [thread overview]
Message-ID: <20011130194347.BCAA75E9D8@zwingli.cygnus.com> (raw)
In-Reply-To: <20011130014034.A29999@nevyn.them.org>
I typo'd in CC'ing the message below to gdb-patches. Daniel had my
approval to commit his change to gnu-v3-abi.c.
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.comb
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
References: <20011126201945.A27754@nevyn.them.org>
<np667wket5.fsf@zwingli.cygnus.com>
<20011127020634.A10010@nevyn.them.org>
<npd723j4lc.fsf@zwingli.cygnus.com>
<20011130014034.A29999@nevyn.them.org>
Bcc: jimb
From: Jim Blandy <jimb@zwingli.cygnus.com>
Date: 30 Nov 2001 12:12:51 -0500
In-Reply-To: Daniel Jacobowitz's message of Fri, 30 Nov 2001 01:40:34 -0500
Message-ID: <np4rncdvxo.fsf@zwingli.cygnus.com>
Lines: 23
X-Mailer: Gnus v5.3/Emacs 19.34
--text follows this line--
Daniel Jacobowitz <drow@mvista.com> writes:
> Jim, can I commit these? It'll make it easier for me to post the
> following batch. Now that GCC emits the information I need (on HEAD at
> least) I'd like to finish this up.
Yes, go ahead.
> I guess that I can commit the gnu-v3-abi bits on my own initiative,
> since no one objected... actually, I guess the values stuff is
> unmaintained too?
Well, officially, yes, but my sense is that values.c is a high-traffic
area, so people would squonk more if you just commit stuff there.
I'll let Andrew tell you the Official Position.
> MAINTAINERS says:
> If there is no maintainer for a given domain then the responsibility
> falls to the head maintainer.
> So I guess I need approval from one of Ye Divine Entities first.
... I'm clearly suffering from a divinity deficiency. But I'll
approve your changes.
WARNING: multiple messages have this Message-ID
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
Date: Fri, 30 Nov 2001 11:42:00 -0000 [thread overview]
Message-ID: <20011130194347.BCAA75E9D8@zwingli.cygnus.com> (raw)
Message-ID: <20011130114200.4h17hbPiE7tnFmuoFfwVVUOcGeU79AC85umEzDns8_w@z> (raw)
In-Reply-To: <20011130014034.A29999@nevyn.them.org>
I typo'd in CC'ing the message below to gdb-patches. Daniel had my
approval to commit his change to gnu-v3-abi.c.
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.comb
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
References: < 20011126201945.A27754@nevyn.them.org >
< np667wket5.fsf@zwingli.cygnus.com >
< 20011127020634.A10010@nevyn.them.org >
< npd723j4lc.fsf@zwingli.cygnus.com >
< 20011130014034.A29999@nevyn.them.org >
Bcc: jimb
From: Jim Blandy <jimb@zwingli.cygnus.com>
Date: 30 Nov 2001 12:12:51 -0500
In-Reply-To: Daniel Jacobowitz's message of Fri, 30 Nov 2001 01:40:34 -0500
Message-ID: <np4rncdvxo.fsf@zwingli.cygnus.com>
Lines: 23
X-Mailer: Gnus v5.3/Emacs 19.34
--text follows this line--
Daniel Jacobowitz <drow@mvista.com> writes:
> Jim, can I commit these? It'll make it easier for me to post the
> following batch. Now that GCC emits the information I need (on HEAD at
> least) I'd like to finish this up.
Yes, go ahead.
> I guess that I can commit the gnu-v3-abi bits on my own initiative,
> since no one objected... actually, I guess the values stuff is
> unmaintained too?
Well, officially, yes, but my sense is that values.c is a high-traffic
area, so people would squonk more if you just commit stuff there.
I'll let Andrew tell you the Official Position.
> MAINTAINERS says:
> If there is no maintainer for a given domain then the responsibility
> falls to the head maintainer.
> So I guess I need approval from one of Ye Divine Entities first.
... I'm clearly suffering from a divinity deficiency. But I'll
approve your changes.
next prev parent reply other threads:[~2001-11-30 19:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 9:24 Daniel Jacobowitz
2001-11-13 9:24 ` Daniel Jacobowitz
2001-11-13 9:34 ` Kevin Buettner
2001-11-26 18:25 ` Kevin Buettner
2001-11-26 21:07 ` Andrew Cagney
2001-11-13 21:56 ` Andrew Cagney
2001-11-14 22:09 ` Jim Blandy
2001-11-27 12:48 ` Jim Blandy
2001-11-26 18:02 ` Daniel Jacobowitz
2001-11-13 18:02 ` Jim Blandy
2001-11-14 9:33 ` Daniel Jacobowitz
2001-11-14 22:39 ` Jim Blandy
2001-11-14 22:41 ` Daniel Jacobowitz
2001-11-27 13:26 ` Daniel Jacobowitz
2001-11-21 13:03 ` Daniel Jacobowitz
2001-11-22 13:53 ` Jim Blandy [this message]
2001-11-30 11:42 ` Jim Blandy
2001-11-29 22:41 ` Daniel Jacobowitz
2001-11-30 8:48 ` Andrew Cagney
2001-11-21 17:30 ` Andrew Cagney
2001-11-30 8:57 ` Daniel Jacobowitz
2001-11-21 23:07 ` Daniel Jacobowitz
2001-11-27 13:16 ` Jim Blandy
2001-11-26 23:08 ` Daniel Jacobowitz
2001-11-26 20:38 ` Jim Blandy
2001-11-26 21:36 ` Daniel Jacobowitz
2001-11-14 0:12 ` Daniel Jacobowitz
2001-11-26 22:05 ` Daniel Berlin
2001-11-14 0:15 ` Daniel Berlin
2001-11-27 7:15 ` Jim Blandy
2001-11-14 13:02 ` Jim Blandy
2001-11-27 7:45 ` Daniel Jacobowitz
2001-11-14 13:55 ` Daniel Jacobowitz
2001-11-26 17:19 ` Daniel Jacobowitz
2001-11-15 14:06 Michael Elizabeth Chastain
2001-11-16 11:52 ` Daniel Berlin
2001-11-27 20:49 ` Daniel Berlin
2001-11-27 20:38 ` Michael Elizabeth Chastain
2001-11-30 9:00 Michael Elizabeth Chastain
2001-11-21 23:07 ` Michael Elizabeth Chastain
2001-11-22 3:17 ` Daniel Jacobowitz
2001-11-30 9:52 ` 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=20011130194347.BCAA75E9D8@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=gdb-patches@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