From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/5] Remove support for old FreeBSD hosts
Date: Wed, 9 Sep 2020 14:19:43 -0700 [thread overview]
Message-ID: <98441312-ebfc-92e3-1867-bf1229c47574@FreeBSD.org> (raw)
In-Reply-To: <20200720173136.10514-1-jhb@FreeBSD.org>
On 7/20/20 10:31 AM, John Baldwin wrote:
> This patch series aims to remove some cruft from the FreeBSD native
> target that isn't needed on modern systems. Most of the changes
> remove support for systems released more than 10 years ago. The last
> change is closer to 9 years ago, but any such systems already fail to
> compile the native target today (and for several recent releases).
> I've yet to receive a single complaint either here or on FreeBSD lists
> about such breakage.
I'd like to push this little series later this week, but since it's
been a while since I posted it I thought I'd give a heads up first.
I don't have any material differences aside from adding and additional
comment in the commit log for patch 2 I mentioned in an earlier
reply to Simon.
--
John Baldwin
prev parent reply other threads:[~2020-09-09 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:31 John Baldwin
2020-07-20 17:31 ` [PATCH 1/5] Assume that PT_LWPINFO is always defined on " John Baldwin
2020-07-20 17:31 ` [PATCH 2/5] Assume KERN_PROC_PATHNAME is present " John Baldwin
2020-07-21 2:16 ` Simon Marchi
2020-07-22 16:44 ` John Baldwin
2020-07-20 17:31 ` [PATCH 3/5] Assume FreeBSD hosts include support for fetching signal information John Baldwin
2020-07-20 17:31 ` [PATCH 4/5] Require kinfo_get_file and kinfo_get_vmmap for FreeBSD hosts John Baldwin
2020-07-20 17:31 ` [PATCH 5/5] Assume FreeBSD kernels always report exec events John Baldwin
2020-08-03 16:19 ` [PATCH 0/5] Remove support for old FreeBSD hosts John Baldwin
2020-09-10 12:24 ` Simon Marchi
2020-09-10 19:56 ` John Baldwin
2020-09-09 21:19 ` John Baldwin [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=98441312-ebfc-92e3-1867-bf1229c47574@FreeBSD.org \
--to=jhb@freebsd.org \
--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).