From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH cygport 0/2] Avoid misbehaviour with llvm-objdump
Date: Tue, 1 Feb 2022 17:25:17 +0000 [thread overview]
Message-ID: <20220201172519.14881-1-jon.turney@dronecode.org.uk> (raw)
Jon Turney (2):
postinst: Never remove an existing .gnu_debuglink
Don't use llvm-objdump
lib/pkg_info.cygpart | 8 --------
lib/src_postinst.cygpart | 35 +++++++++++++++++++----------------
2 files changed, 19 insertions(+), 24 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-01 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:25 Jon Turney [this message]
2022-02-01 17:25 ` [PATCH cygport 1/2] postinst: Never remove an existing .gnu_debuglink Jon Turney
2022-02-01 19:22 ` Corinna Vinschen
[not found] ` <eef4ada5-0ace-d828-c163-988390aa35e0@dronecode.org.uk>
2022-02-02 9:31 ` Corinna Vinschen
2022-02-01 17:25 ` [PATCH cygport 2/2] Don't use llvm-objdump Jon Turney
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=20220201172519.14881-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).