From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: jhb@FreeBSD.org, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries.
Date: Wed, 28 Nov 2018 19:21:00 -0000 [thread overview]
Message-ID: <83lg5ddn38.fsf@gnu.org> (raw)
In-Reply-To: <6b48a787-dec3-6be7-9a3d-7bb0284bc11c@redhat.com> (message from Pedro Alves on Wed, 28 Nov 2018 18:34:42 +0000)
> Cc: gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 28 Nov 2018 18:34:42 +0000
>
> IMO, a user reading the "catch syscall" bits in the manual isn't
> going to remember to look up the FreeBSD-specific info in a
> different node. Unless we add some xrefs.
Then let's add them.
next prev parent reply other threads:[~2018-11-28 19:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 20:04 [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin
2018-11-09 20:04 ` [PATCH v3 1/3] Change get_syscalls_by_group to append to an existing vector of integers John Baldwin
2018-11-09 20:04 ` [PATCH v3 2/3] Add an optional "alias" attribute to syscall entries John Baldwin
2018-11-09 20:18 ` Eli Zaretskii
2018-11-16 17:44 ` John Baldwin
2018-11-16 19:37 ` Eli Zaretskii
2018-11-27 17:13 ` Pedro Alves
2018-11-27 21:54 ` John Baldwin
2018-11-28 6:31 ` Eli Zaretskii
2018-11-28 12:19 ` Pedro Alves
2018-11-28 17:22 ` John Baldwin
2018-11-28 17:44 ` Eli Zaretskii
2018-11-28 18:00 ` John Baldwin
2018-11-28 18:31 ` Eli Zaretskii
2018-11-28 18:34 ` Pedro Alves
2018-11-28 19:15 ` John Baldwin
2018-11-28 19:21 ` Eli Zaretskii [this message]
2018-11-09 20:04 ` [PATCH v3 3/3] Update the FreeBSD system call table to match FreeBSD 12.0 John Baldwin
2018-11-26 20:31 ` [PATCH v3 0/3] Update FreeBSD's syscall table John Baldwin
2018-11-27 17:20 ` Pedro Alves
2018-11-27 20:00 ` John Baldwin
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=83lg5ddn38.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).