From: Pedro Alves <pedro@palves.net>
To: 紀重禕 <demonic@csie.io>, simark@simark.ca
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] breakpoint.c: Fix advance/until and multiple locations
Date: Thu, 27 Aug 2020 21:27:00 +0100 [thread overview]
Message-ID: <44e325dc-ea57-53ed-117c-e6efb05fec39@palves.net> (raw)
In-Reply-To: <CA+YVB3QeT0n54--JLtjvumMt3xHiZ=HLEgi0SRvg0SBQ2rYfGQ@mail.gmail.com>
On 8/27/20 3:17 AM, 紀重禕 wrote:
> Hi Simon,
>
> Pedro Alves actually did a better and complete patch! Sorry to take up your
> time.
I was the one who created the bug reports and I already had
the fixes written before I created them.
I'm very sorry that I didn't say so in the bug reports, which
would have avoided you the work! I'll keep this in mind for
the next time.
I never imagined that someone else would run into the bug and
write a patch so quickly! What a coincidence.
Thanks for contributing. Please don't be shy about fixing
more bugs and posting more patches! :-)
Thanks,
Pedro Alves
prev parent reply other threads:[~2020-08-27 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 15:06 紀重禕
2020-08-27 2:03 ` Simon Marchi
2020-08-27 2:17 ` 紀重禕
2020-08-27 2:22 ` Simon Marchi
2020-08-27 20:27 ` Pedro Alves [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=44e325dc-ea57-53ed-117c-e6efb05fec39@palves.net \
--to=pedro@palves.net \
--cc=demonic@csie.io \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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