From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Remove all traces of Unixware.
Date: Tue, 11 Dec 2012 12:46:00 -0000 [thread overview]
Message-ID: <837gooah9k.fsf@gnu.org> (raw)
In-Reply-To: <50C71AE7.4070102@redhat.com>
> Date: Tue, 11 Dec 2012 11:37:11 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> gdb/
> 2012-12-11 Pedro Alves <palves@redhat.com>
>
> * configure.ac (detect type of /proc): Remove Unixware handling.
> * configure: Regenerate.
> * proc-api.c (ioctl_table) [PIOCLSTATUS]: Don't mention Unixware.
> (ioctl_table) [PCRESET]: Remove entry.
> * proc-events.c (SYS_lwp_create, SYS_lwp_exit, SYS_lwp_wait)
> (SYS_lwp_self, SYS_lwp_info, SYS_lwp_private, SYS_lwp_kill)
> (SYS_lwp_suspend, SYS_lwp_continue): Don't define.
> * proc-why.c (pr_why_table) [PR_SUSPENDED]: Don't mention Unixware.
> * procfs.c: Remove all UNIXWARE guarded code, and all traces of
> Unixware in comments throughout.
> * i386-tdep.c (i386_svr4_sigtramp_p): Don't match _sigacthandler,
> and remove mention of Unixware.
>
> gdb/doc/
> 2012-12-11 Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo: Remove all mentions of Unixware throughout.
The documentation part is obvious. Thanks.
next prev parent reply other threads:[~2012-12-11 12:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 17:37 [PATCH] solib-svr4.c: Remove old SCO-related code Pedro Alves
2012-12-10 16:44 ` Pedro Alves
2012-12-10 18:02 ` [PATCH 1/2] Put a NT_PSTATUS note on solaris cores Pedro Alves
2012-12-11 3:04 ` Joel Brobecker
2012-12-11 12:22 ` Pedro Alves
2012-12-11 15:12 ` Joel Brobecker
2012-12-11 15:16 ` Mark Kettenis
2012-12-11 16:45 ` Pedro Alves
2012-12-10 18:04 ` [PATCH 2/2] Remove all traces of Unixware Pedro Alves
2012-12-10 19:24 ` Tom Tromey
2012-12-11 2:57 ` Joel Brobecker
2012-12-11 11:37 ` Pedro Alves
2012-12-11 12:46 ` Eli Zaretskii [this message]
2012-12-11 4:20 ` Yao Qi
2012-12-11 10:59 ` Pedro Alves
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=837gooah9k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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