Linux Manual Pages development
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] syscall.2: add arm64 and mips
Date: Sun, 15 Feb 2015 16:13:02 +0100	[thread overview]
Message-ID: <54E0B77E.5090306@gmail.com> (raw)
In-Reply-To: <20150215104609.GF32251@vapier>

On 02/15/2015 11:46 AM, Mike Frysinger wrote:
> On 17 Jan 2015 23:22, Kees Cook wrote:
>> --- a/man2/syscall.2
>> +++ b/man2/syscall.2
>> @@ -36,6 +36,8 @@
>>  .\"
>>  .\" 2002-03-20  Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
>>  .\"	- adopted for Linux
>> +.\" 2015-01-17, Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>> +.\"	Added mips and arm64.
>>  .\"
> 
> can we scrub changelogs from the man pages in general ?  they're usually 
> incomplete and rarely provide more than `git log -p`.

Yes, I tend to discourage them these days, but don't always worry too much if
someone adds them to  patch.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-02-15 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18  7:22 [PATCH] syscall.2: add arm64 and mips Kees Cook
     [not found] ` <20150118072204.GA12237-0X9Bc/hWBUTk6RaD4rd5nQ@public.gmane.org>
2015-01-18 11:58   ` Michael Kerrisk (man-pages)
     [not found]     ` <54BB9FF3.5070706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-20 19:02       ` Kees Cook
2015-02-15 10:46   ` Mike Frysinger
2015-02-15 15:13     ` Michael Kerrisk (man-pages) [this message]
     [not found]       ` <54E0B77E.5090306-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-15 17:51         ` Mike Frysinger
2015-02-16 19:30           ` Kees Cook
     [not found]             ` <CAGXu5jKyt2ZsFLhYrQpWfTWdipHYyCy1En3FObxYqxHuiLGgGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-17  4:02               ` Mike Frysinger
2015-02-17  4:53                 ` Michael Kerrisk (man-pages)

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=54E0B77E.5090306@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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