Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tromey@redhat.com>,
	 Mark Kettenis <mark.kettenis@xs4all.nl>,
	 gdb-patches@sourceware.org
Subject: Re: [patch] Set calling convention of methods
Date: Tue, 03 Nov 2009 09:43:00 -0000	[thread overview]
Message-ID: <DDBF6E12-FA77-4BA0-AF9B-6B39A1CA857A@elis.ugent.be> (raw)
In-Reply-To: <20090930173230.GG10338@adacore.com>


On 30 Sep 2009, at 19:32, Joel Brobecker wrote:

>> Jonas> Later on, Tom clarified that he thought that the gdb and gcc  
>> versions
>> Jonas> of dwarf2.h should actually be merged into a single copy,  
>> but that I
>> Jonas> shouldn't worry about this since the divergence started  
>> before my
>> Jonas> patch: http://sourceware.org/ml/gdb-patches/2009-04/msg00099.html
>>
>> I've merged these now.
>>
>> I think the usual approach for such merged files is that GCC is the
>> master copy.
>
> Confirmed. It's written plain as day in the header.  The sticky part
> is that Jonas does NOT have copyright assignment on file for GCC, as
> far as I can tell...

I've pinged my dwarf2.h thrice on the gcc-patches list in the mean  
time (always inline, because it doesn't contain any lines >= 80  
chars), the last time mentioning that I now also have a copyright  
assignment on file for GCC. I haven received so much as an  
acknowledgment.

Here's the last ping I did: http://gcc.gnu.org/ml/gcc-patches/2009-10/msg01788.html 
  (it's only from Friday, but given my past experiences, I don't  
expect it suddenly to be picked up after getting buried under a couple  
days extra mail).

I don't know what else to do.


Jonas


  parent reply	other threads:[~2009-11-03  9:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 19:51 Jonas Maebe
2009-04-10 17:34 ` Tom Tromey
2009-04-20  8:40   ` Jonas Maebe
2009-04-20 18:27     ` Tom Tromey
2009-04-22 17:45       ` Jonas Maebe
2009-04-22 19:22         ` Tom Tromey
2009-04-22 22:16         ` Mark Kettenis
2009-06-04  8:23           ` Jonas Maebe
2009-06-04 18:19             ` Tom Tromey
2009-06-10 20:44               ` Jonas Maebe
2009-06-18 21:45                 ` Fwd: " Jonas Maebe
2009-09-30  0:02                 ` Joel Brobecker
2009-09-30 11:18                   ` Jonas Maebe
2009-09-30 14:54                     ` Jonas Maebe
2009-09-30 15:22                       ` Mark Kettenis
2009-09-30 16:25                       ` Joel Brobecker
2009-10-01  9:18                         ` Jonas Maebe
2009-10-01 22:04                           ` Joel Brobecker
2009-10-02  9:21                           ` Mark Kettenis
2009-09-30 16:10                     ` Joel Brobecker
2009-09-30 17:36                       ` Joel Brobecker
2009-09-30 16:47                     ` Tom Tromey
2009-09-30 17:32                       ` Joel Brobecker
2009-09-30 17:35                         ` Tom Tromey
2009-10-01  9:21                           ` Jonas Maebe
2009-11-03  9:43                         ` Jonas Maebe [this message]
2009-11-03 14:19                           ` Joel Brobecker
2009-07-06 20:50               ` Jonas Maebe

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=DDBF6E12-FA77-4BA0-AF9B-6B39A1CA857A@elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@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