From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] Provide access to non SEC_HAS_CONTENTS core file sections
Date: Wed, 13 May 2020 10:44:13 -0700 [thread overview]
Message-ID: <20200513104413.7fa3eb2b@f31-4.lan> (raw)
In-Reply-To: <20200512014032.0a3bdfa1@f31-4.lan>
On Tue, 12 May 2020 01:40:32 -0700
Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org> wrote:
> > This Change-Id line should be at the bottom of the commit log.
> > Or removed entirely since we're not relying on it anymore.
>
> I think the Change-Id might have been placed there due to the use of
> "---" as the scissors line demarcating the test program. Git may have
> thought it was the start of a diff. But that's just a guess.
FWIW, I ended up removing the script which was added for gerrit.
Kevin
next prev parent reply other threads:[~2020-05-13 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 0:43 [PATCH 0/4] Fix BZ 25631 - core file memory access problem Kevin Buettner
2020-03-05 0:43 ` [PATCH 4/4] Test ability to access unwritten-to mmap data in core file Kevin Buettner
2020-03-25 17:25 ` Keith Seitz
2020-03-05 0:43 ` [PATCH 2/4] Add function for partitioning/splitting a section table Kevin Buettner
2020-03-25 17:25 ` Keith Seitz
2020-03-05 0:43 ` [PATCH 1/4] Remove hack for GDB which sets the section size to 0 Kevin Buettner
2020-03-18 16:28 ` Kevin Buettner
2020-05-04 18:09 ` Jan Kratochvil
2020-03-05 0:43 ` [PATCH 3/4] Provide access to non SEC_HAS_CONTENTS core file sections Kevin Buettner
2020-03-25 17:25 ` Keith Seitz
2020-03-29 13:18 ` Pedro Alves
2020-05-03 7:21 ` Kevin Buettner
2020-05-03 11:07 ` H.J. Lu
2020-05-03 19:06 ` Kevin Buettner
2020-05-12 8:40 ` Kevin Buettner
2020-05-13 17:44 ` Kevin Buettner [this message]
2020-05-20 12:05 ` Pedro Alves
2020-05-20 16:04 ` Pedro Alves
2020-03-18 16:29 ` [PATCH 0/4] Fix BZ 25631 - core file memory access problem Kevin Buettner
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=20200513104413.7fa3eb2b@f31-4.lan \
--to=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).