From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 2/2] Fix an undefined behavior in record_line
Date: Wed, 1 Apr 2020 21:01:44 +0200 [thread overview]
Message-ID: <AM6PR03MB5170459B220853428A129E74E4C90@AM6PR03MB5170.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <877dyz2g2u.fsf@tromey.com>
On 4/1/20 8:53 PM, Tom Tromey wrote:
>>>>>> "Bernd" == Bernd Edlinger <bernd.edlinger@hotmail.de> writes:
>
> Bernd> One last question, does this approval also include
> Bernd> part 1/2 "Fix the resizing condition of the line table" ?
>
> Yeah... I sent a separate note about that.
>
> https://sourceware.org/pipermail/gdb-patches/2020-April/167214.html
>
> Anyway, no worries, please go ahead :)
>
> Tom
>
Ah, interesting, not in my inbox and not in my spam folder either,
I think I did recently also not receive a response to one of my linux
patches, which I also saw only on the mailing list archives, but
I was wondering why I did not receive it in the first place.
Did this message bounce, or is it grey-listed, I don't think hotmail.de
does this, but you never know.
Thanks
Bernd.
next prev parent reply other threads:[~2020-04-01 19:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 3:50 Bernd Edlinger
2020-04-01 16:23 ` Tom Tromey
2020-04-01 16:52 ` Bernd Edlinger
2020-04-01 18:40 ` Bernd Edlinger
2020-04-01 18:53 ` Tom Tromey
2020-04-01 19:01 ` Bernd Edlinger [this message]
2020-04-03 22:53 ` Luis Machado
2020-04-04 4:21 ` Bernd Edlinger
2020-04-04 7:06 ` Bernd Edlinger
2020-04-04 13:56 ` Luis Machado
2020-04-04 16:06 ` Bernd Edlinger
2020-04-04 16:22 ` Luis Machado
2020-04-04 16:34 ` Bernd Edlinger
2020-04-04 22:55 ` Andrew Burgess
2020-04-05 0:12 ` Bernd Edlinger
2020-04-04 23:03 ` Andrew Burgess
2020-04-06 17:44 ` Andrew Burgess
2020-04-06 18:48 ` Bernd Edlinger
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=AM6PR03MB5170459B220853428A129E74E4C90@AM6PR03MB5170.eurprd03.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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