public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Seonghun Lim <wariua-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] acct.2: wfix
Date: Thu, 9 Nov 2017 09:41:30 +0100	[thread overview]
Message-ID: <0510c60a-5818-86e5-5dde-c0ad3e307bb0@gmail.com> (raw)
In-Reply-To: <b4fe25b7-8ef8-a5aa-f5d3-e84d483d4233-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 11/09/2017 09:39 AM, Michael Kerrisk (man-pages) wrote:
> Hello Seonghun Lim
> 
> I have applied all of your recent patches.

Sorry, I forgot to say: thank you for the many nice
little cleanups!

Cheers,

Michael

> On 11/09/2017 09:24 AM, Michael Kerrisk (man-pages) wrote:
>> Hello Seonghun Lim,
>>
>> On 11/09/2017 09:06 AM, Michael Kerrisk (man-pages) wrote:
>>> Hello Seonghun Lim,
>>>
>>> This is a nice series of patches that you've sent. But none
>>> of the patches applies against upstream. Looking at the source
>>> of the mail messages, there are some strange character sequences
>>> at the start of various lines. Could you fix up
>>> and resubmit the patch series please?
>>
>> Okay -- I've found a way to manually fix the patches that is not too 
>> burdensome. But there's definitely some character set problem with
>> your patches... No need to resubmit these patches though.
>>
>> Cheers,
>>
>> Michael
>>
>>> On 11/08/2017 08:00 AM, Seonghun Lim wrote:
>>>>  man2/acct.2 | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/man2/acct.2 b/man2/acct.2
>>>> index 27b0c5cf4..f9efe437f 100644
>>>> --- a/man2/acct.2
>>>> +++ b/man2/acct.2
>>>> @@ -107,7 +107,7 @@ was too long.
>>>>  The system-wide limit on the total number of open files has been reached.
>>>>  .TP
>>>>  .B ENOENT
>>>> -The specified filename does not exist.
>>>> +The specified file does not exist.
>>>>  .TP
>>>>  .B ENOMEM
>>>>  Out of memory.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 


-- 
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

      parent reply	other threads:[~2017-11-09  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08  7:00 [patch] acct.2: wfix Seonghun Lim
     [not found] ` <9bbfbda5-b614-314d-dad9-ad2ea789d4d1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-09  8:06   ` Michael Kerrisk (man-pages)
     [not found]     ` <a843da9a-b6a3-b698-9fbf-460ad5b1e361-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-09  8:24       ` Michael Kerrisk (man-pages)
     [not found]         ` <51b60a7e-8f3b-379a-cd4f-c2a8c55f3af7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-09  8:39           ` Michael Kerrisk (man-pages)
     [not found]             ` <b4fe25b7-8ef8-a5aa-f5d3-e84d483d4233-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-09  8:41               ` Michael Kerrisk (man-pages) [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=0510c60a-5818-86e5-5dde-c0ad3e307bb0@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wariua-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox