From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Sat, 02 Jul 2016 01:16:00 -0000 [thread overview]
Message-ID: <a1eb4878-2dfe-71c6-f157-7df1a5a268e9@gmail.com> (raw)
In-Reply-To: <0896c322-0ac9-b60e-daaf-09355307e19b@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]
On 30.06.2016 22:13, LRN wrote:
> On 30.06.2016 21:56, Eli Zaretskii wrote:
>> On Thu, 30 Jun 2016 21:36:12 +0300, LRN wrote:
>>> On 30.06.2016 20:42, Eli Zaretskii wrote:
>>>> On Thu, 30 Jun 2016 20:18:52 +0300, LRN wrote:
>>>>> I did. What did i do wrong? Had a single space (instead of two spaces)
>>>>> after the name? Used "Fix PR gdb/14529" at the end instead of "PR
>>>>> gdb/14529" at the beginning? No function name in parentheses (should
>>>>> it have been signal_event_command?)?
>>>>
>>>> The latter.
>>>>
>>>
>>> Fixed patches attached.
>>
>> Thanks. One last nit is that the ChangeLog entry for gdb.texinfo
>> should also state a "function name", which is the node name where you
>> made the changes.
>>
>
> Fixed patch is attached.
>
So, anyway, is anything else expected of me? When should i expect to see
the patches pushed?
I also have a different patch that i want to submit. Should i do it now, in
a separate email, or wait until this one is through?
--
O< ascii ribbon - stop html email! - www.asciiribbon.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-02 1:16 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
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 [this message]
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=a1eb4878-2dfe-71c6-f157-7df1a5a268e9@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