Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] x86 CFI extensions
Date: Mon, 26 Sep 2005 07:04:00 -0000	[thread overview]
Message-ID: <4337B9F1.76F0.0078.0@novell.com> (raw)
In-Reply-To: <20050926012418.GB22284@nevyn.them.org>

>>> Daniel Jacobowitz <drow@false.org> 26.09.05 03:24:18 >>>
>On Fri, Sep 23, 2005 at 09:40:15AM +0200, Jan Beulich wrote:
>> >>> Mark Kettenis <mark.kettenis@xs4all.nl> 09/21/05 10:02 PM >>>
>> >This is ok.  However, I don't see your name listed in gdb/MAINTAINERS.
>> >Do you have a valid copyright assignment for GDB?
>> 
>> From all I can tell I do (for binutils, gcc, and gdb). I didn't care to
>> add myself to gdb/MAINTAINERS, as there's really not a lot I'm currently
>> doing with/for it specifically (binutils changes to opcodes/ certainly
>> affect it, though).
>> 
>> So, am are you OK with me going ahead and committing the patch?
>
>Could you please (A) commit the patch, and (B) commit and post a patch
>adding yourself to MAINTAINERS?  I realize you don't intend to do
>active GDB development; that's OK, most of the other people who've
>ended up in that list don't either.

Below/Done.

Jan

gdb/
2005-09-26  Jan Beulich  <jbeulich@novell.com>

	* MAINTAINERS (Write After Approval): Add myself.

--- /home/jbeulich/src/gdb/mainline/2005-09-13/gdb/MAINTAINERS	2005-08-18 08:51:36.000000000 +0200
+++ 2005-09-13/gdb/MAINTAINERS	2005-09-26 08:59:37.421637560 +0200
@@ -301,6 +301,7 @@ David Anderson					davea@sgi.com 
 John David Anglin				dave.anglin@nrc-cnrc.gc.ca 
 Shrinivas Atre					shrinivasa@kpitcummins.com 
 Scott Bambrough					scottb@netwinder.org 
+Jan Beulich					jbeulich@novell.com 
 Jim Blandy					jimb@redhat.com 
 Philip Blundell					philb@gnu.org 
 Per Bothner					per@bothner.com 



  reply	other threads:[~2005-09-26  7:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  7:42 Jan Beulich
2005-09-23  8:03 ` Eli Zaretskii
2005-09-23 12:57   ` Daniel Jacobowitz
2005-09-26  1:24 ` Daniel Jacobowitz
2005-09-26  7:04   ` Jan Beulich [this message]
     [not found] <432070850200007800024465@emea1-mh.id2.novell.com>
     [not found] ` <20050908154645.GN3966@smtp.west.cox.net>
     [not found]   ` <43207BA30200007800024502@emea1-mh.id2.novell.com>
     [not found]     ` <20050908161334.GP3966@smtp.west.cox.net>
     [not found]       ` <43214D2D02000078000247B5@emea1-mh.id2.novell.com>
     [not found]         ` <20050910055836.GA28662@twiddle.net>
     [not found]           ` <4325448C0200007800024DF5@emea1-mh.id2.novell.com>
     [not found]             ` <20050912074914.GA31047@twiddle.net>
2005-09-13 16:17               ` Jan Beulich
2005-09-17 20:59                 ` Daniel Jacobowitz
2005-09-17 22:32                   ` Mark Kettenis
2005-09-17 22:40                     ` Daniel Jacobowitz
2005-09-19  7:26                     ` Jan Beulich
2005-09-21 20:02                       ` Mark Kettenis
2005-09-22  8:22                         ` Richard Henderson
2005-09-22 12:48                           ` 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=4337B9F1.76F0.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.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