Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Tue, 02 Oct 2012 12:57:00 -0000	[thread overview]
Message-ID: <506AE4C6.9010304@gmail.com> (raw)
In-Reply-To: <20121002124819.GB3028@adacore.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02.10.2012 16:48, Joel Brobecker wrote:
>>> I have a copyright assignment filed for GNUtls [1], would that
>>> suffice?
> 
> Unfortunately, that's not enough. It needs to include GDB (you
> also have the option of saying "ANY" and be covered for all
> projects). Do you want to start the paperwork?
> 
Not now. Maybe later. I'll up this thread when i'm ready.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQauTDAAoJEOs4Jb6SI2CwO/IH/2a6EtKmEEk9jEOKSZGQL63p
ai7xK0wjbx9hUWhhG+MkPKQoi1PHzeeHaOof6SI4VaYg5oYPn7mekGarlwEWxHzZ
L51WK4K8h3AT4h3cLafsU37WFcyb3/JFAl2cvnQvTJUZM1PfzxGTnE4jH0b/539a
wGXJ1Si9HkMWKNzUM6IcRGg9epOSygHEwwEE8BQAUovsOmhxr1bfzMFtXb3CCRPU
asJJK9OBhSdDwzc4zPpkOlwmZ4Mn6k6J6yYxKRlt/lDucpqNIMcvINr/HrxeV4mu
XmRGEtZl9GSS8siYdr2l7el9gZBEMMVMhAu/WfpCG1YsPgqHiMTivl0JLt/GX3k=
=fksf
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-10-02 12:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 17:55 LRN
2012-08-31 14:53 ` Eli Zaretskii
2012-08-31 15:37   ` Christopher Faylor
2012-08-31 15:40     ` LRN
2012-08-31 15:37   ` LRN
2012-09-10  2:22     ` LRN
2012-09-10 18:15       ` Tom Tromey
2012-09-10 18:32         ` LRN
2012-09-11 18:21       ` Pedro Alves
2012-09-11 18:27         ` LRN
2012-09-11 18:30           ` Pedro Alves
2012-09-11 18:09     ` Pedro Alves
2012-09-11 18:23       ` LRN
2012-09-11 18:27         ` Pedro Alves
2012-09-11 18:31           ` LRN
2012-09-29 12:42           ` LRN
2012-09-29 13:05             ` Eli Zaretskii
2012-09-29 19:32               ` LRN
2012-09-30  7:51                 ` Eli Zaretskii
2012-09-30 12:46                   ` LRN
2012-10-01 13:18                     ` Eli Zaretskii
2012-10-01 16:22                       ` LRN
2012-10-01 22:37 ` Sergio Durigan Junior
2012-10-01 22:48   ` LRN
2012-10-02  5:53     ` Sergio Durigan Junior
2012-10-02 12:48       ` Joel Brobecker
2012-10-02 12:57         ` LRN [this message]
2016-06-30 13:17           ` LRN
2016-06-30 15:25             ` Eli Zaretskii
2016-06-30 15:44               ` LRN
2016-06-30 16:23                 ` Eli Zaretskii
2016-06-30 17:19                   ` LRN
2016-06-30 17:42                     ` Eli Zaretskii
2016-06-30 18:36                       ` LRN
2016-06-30 18:57                         ` Eli Zaretskii
2016-06-30 19:14                           ` LRN
2016-07-02  1:16                             ` LRN
2016-07-02  7:48                               ` Eli Zaretskii
2016-07-10 13:06                                 ` LRN
2016-07-10 14:55                                   ` Eli Zaretskii
2016-07-18 10:08                                     ` LRN
2016-07-19 19:10                                       ` Eli Zaretskii
2016-07-20  4:43                                         ` LRN
2016-07-23  8:41                                           ` Eli Zaretskii

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=506AE4C6.9010304@gmail.com \
    --to=lrn1986@gmail.com \
    --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