All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgi Naydenov <gnaydenov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: man-pages bug- syslog(3) grammar
Date: Fri, 25 Apr 2014 00:02:11 +0300	[thread overview]
Message-ID: <53597BD3.5040501@gmail.com> (raw)
In-Reply-To: <CAKgNAkjGzM-P3Ce1TnBKn0r9xr1W4bjS+S9zCub2=gioWFVQ8w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


Ah, ok then. Thanks for your reply and sorry for the spam ;)

Best regards,
Georgi


На 4/24/2014 8:03 PM, Michael Kerrisk (man-pages) написа:
> Hi Georgi!
>
> On Wed, Apr 23, 2014 at 2:17 PM, Georgi Naydenov <gnaydenov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Hello Michael,
>> I guess that's your email here. First, thank you for your excellent book!
>> (We met at the OpenFest in Sofia, Bulgaria a few years ago and luckily you
>> had some copies with you. :)
> Yes, I remember.
>
>> About the pages - nothing special but what do you think about the commas
>> when describing notice message priorty here:
>> http://man7.org/linux/man-pages/man3/syslog.3.html
>> and also in syslog(3) at least on Fedora, CentOS6 and RHEL6/7beta.
>>
>>         LOG_NOTICE     normal, but significant, condition
>>
>> Shouldn't be "significant condition"? For example, as specified in RFC5424
>> (http://tools.ietf.org/html/rfc5424):
>>
>>                        ....
>>                5       Notice: normal but significant condition
>>                6       Informational: informational messages
>>                7       Debug: debug-level messages
>>
>>                Table 2. Syslog Message Severities
> Either form works, so I'll leave as is.
>
> Cheers,
>
> Michael

--
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:[~2014-04-24 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5357AF43.8080102@gmail.com>
     [not found] ` <5357AF43.8080102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-24 17:03   ` man-pages bug- syslog(3) grammar Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAkjGzM-P3Ce1TnBKn0r9xr1W4bjS+S9zCub2=gioWFVQ8w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-24 21:02       ` Georgi Naydenov [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=53597BD3.5040501@gmail.com \
    --to=gnaydenov-re5jqeeqqe8avxtiumwx3w@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.