All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] syscall.2: add arm64 and mips
Date: Mon, 16 Feb 2015 23:02:47 -0500	[thread overview]
Message-ID: <20150217040247.GA4400@vapier> (raw)
In-Reply-To: <CAGXu5jKyt2ZsFLhYrQpWfTWdipHYyCy1En3FObxYqxHuiLGgGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

On 16 Feb 2015 11:30, Kees Cook wrote:
> On Sun, Feb 15, 2015 at 9:51 AM, Mike Frysinger wrote:
> > On 15 Feb 2015 16:13, Michael Kerrisk (man-pages) wrote:
> >> 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.
> >
> > in this case, i think Kees was following apparent convention rather than
> > thinking he always add one.  so i'm suggesting we help out at least the
> > people who are just trying to DTRT by scrubbing the tree of existing ones
> > that aren't useful.
> 
> Yeah, I tend to try to follow the convention in the file. It's wasn't
> clear what to do. I'm happy to send a patch to wipe my entries, if
> that's desired.

i don't think we need to make you do that one off :).  if Michael is happy with 
scrubbing the code base, lets go that route.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-02-17  4:02 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)
     [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 [this message]
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=20150217040247.GA4400@vapier \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.