Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCHv2] Make "skip" work on inline frames
Date: Wed, 30 Oct 2019 20:18:00 -0000	[thread overview]
Message-ID: <708fdc14-21ca-76dd-c0cd-0cb09b6b2eac@simark.ca> (raw)
In-Reply-To: <c7fdf612-d19c-c3b1-39f7-9a13772c68d3@hotmail.de>

On 2019-10-30 4:05 p.m., Bernd Edlinger wrote:
> There should be an assignment on file, although it is signed by my employer
> Softing Industrial Automation GmbH on Oct 25 2012 and countersigned by
> John Sullivan on Dec 17 2012
> The work that is intended to be covered by this assignment is mine.
> 
> I am also the maintainer of the GNU Mempool package:
> https://www.gnu.org/software/mempool/
> so I should be known to gnu.org, but maybe something got lost.
> 
> Is this assignment sufficient for contributing to gdb?
> 
> 
> Thanks
> Bernd.
> 

Hi Bernd,

The only assignment I see under Softing Industrial Automation is for GNU eCos, with
the date 2012-12-20, which fits with the date you gave.  Unfortunately, the assignments
are per-project, so you'll need to be covered by one for GDB too.

I also don't find anything for Mempool in the copyright.list file, which is strange.
If you are contributing code to a GNU project, you should normally have signed such
an copyright assignment for it in the past.  Do you remember doing so for Mempool?

Simon


      reply	other threads:[~2019-10-30 20:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 12:52 [PATCH] " Bernd Edlinger
2019-10-19  4:40 ` Bernd Edlinger
2019-10-20  6:48   ` [PATCHv2] " Bernd Edlinger
2019-10-26  8:06     ` [PING] " Bernd Edlinger
2019-10-27  1:52     ` Simon Marchi
2019-10-27  2:18       ` Simon Marchi
2019-10-30 21:56         ` Bernd Edlinger
2019-10-31 16:42           ` Pedro Alves
2019-10-31 16:53             ` Simon Marchi
2019-10-31 18:00               ` Pedro Alves
2019-10-31 19:19                 ` [PATCHv3] " Bernd Edlinger
2019-11-24 11:22                   ` [PATCHv4] " Bernd Edlinger
2019-12-01 20:46                     ` [PING] " Bernd Edlinger
2019-12-02  2:34                     ` Simon Marchi
2019-12-02 16:47                       ` [PATCHv5] " Bernd Edlinger
2019-12-03  4:22                         ` Simon Marchi
2019-12-14 13:55                         ` [PING] " Bernd Edlinger
2019-12-15  0:46                         ` Simon Marchi
2019-12-15 11:25                           ` [PATCHv6] " Bernd Edlinger
2019-12-15 13:12                             ` Simon Marchi
2019-12-15 18:18                               ` Bernd Edlinger
2019-12-17  2:01                                 ` Simon Marchi
2019-12-17 13:00                                   ` Bernd Edlinger
2019-10-30 20:06       ` [PATCHv2] " Bernd Edlinger
2019-10-30 20:18         ` Simon Marchi [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=708fdc14-21ca-76dd-c0cd-0cb09b6b2eac@simark.ca \
    --to=simark@simark.ca \
    --cc=bernd.edlinger@hotmail.de \
    --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