All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon <jg-hus3n9K41k0@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: strncpy, strcat and memalign
Date: Mon, 30 Aug 2010 11:45:03 +0100	[thread overview]
Message-ID: <4C7B8BAF.9040605@jguk.org> (raw)
In-Reply-To: <AANLkTinYg=ke4ju2L+6aqGQNEvzB4JuomfFUrV9sRKkG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello Michael,

Thanks for your reply.

Michael Kerrisk wrote, On 29/08/10 08:08:
[.]
> The HTML-rendered man pages at linux.die.net are created by someone
> unknown to me. They are also years out of date.
> 
> For up-to-date HTML renderings, produced by me, see
> http://www.kernel.org/doc/man-pages/online_pages.html

Perfect! These are great. It is a shame those die.net are still 
comming up first on google "linux man strncpy".

I'll just refer to the your kernel.org link now.

[.]
> I tend to avoid NUL, simply because it is so easy to visually confuse
> with "NULL".
> 
> Other than that, I think the pages pretty consistently use '\0',
> "terminating null byte", and "null-terminated string". I think this is
> okay.

This looks great, very clear in these up to date man pages.

Best regards, Jon
--
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:[~2010-08-30 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01  0:10 strncpy, strcat and memalign Jon Grant
     [not found] ` <AANLkTimhujBTS5G_Q3BoFrVe1DKXsftrN14eMC5BD+di-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-29  7:08   ` Michael Kerrisk
     [not found]     ` <AANLkTinYg=ke4ju2L+6aqGQNEvzB4JuomfFUrV9sRKkG-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-30 10:45       ` Jon [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=4C7B8BAF.9040605@jguk.org \
    --to=jg-hus3n9k41k0@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.