From: Aaron Merey <amerey@redhat.com>
To: elfutils-devel@sourceware.org
Cc: Aaron Merey <amerey@redhat.com>
Subject: [PATCH OB] Changelog: Update entries from previous commits.
Date: Tue, 1 Nov 2022 20:14:41 -0400 [thread overview]
Message-ID: <20221102001441.64481-1-amerey@redhat.com> (raw)
Pushed as obvious.
Update Changelogs with details from commits 04b1a3aa and 054b3bde9.
Signed-off-by: Aaron Merey <amerey@redhat.com>
---
debuginfod/ChangeLog | 4 ++++
tests/ChangeLog | 5 +++++
2 files changed, 9 insertions(+)
diff --git a/debuginfod/ChangeLog b/debuginfod/ChangeLog
index 92a880f8..50668e61 100644
--- a/debuginfod/ChangeLog
+++ b/debuginfod/ChangeLog
@@ -1,3 +1,7 @@
+2022-11-01 Aaron Merey <amerey@redhat.com>
+
+ * debuginfod-client.c (path_escape): Add early return.
+
2022-10-31 Aaron Merey <amerey@redhat.com>
* Makefile.am (libdebuginfod_so_LDLIBS): Add libelf.
diff --git a/tests/ChangeLog b/tests/ChangeLog
index fb0dce82..b656029f 100644
--- a/tests/ChangeLog
+++ b/tests/ChangeLog
@@ -1,3 +1,8 @@
+2022-11-01 Aaron Merey <amerey@redhat.com>
+
+ * run-debuginfod-section.sh (RPM_BUILDID): Use buildid from non-zstd
+ compressed rpm.
+
2022-10-31 Aaron Merey <amerey@redhat.com>
* Makefile.am (TESTS): Add run-debuginfod-section.sh.
--
2.37.3
reply other threads:[~2022-11-02 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221102001441.64481-1-amerey@redhat.com \
--to=amerey@redhat.com \
--cc=elfutils-devel@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).