All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Simon Paillard
	<spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] mcheck.3: typo in compiler flag
Date: Fri, 27 Dec 2013 07:28:18 +1300	[thread overview]
Message-ID: <52BC7542.1000905@gmail.com> (raw)
In-Reply-To: <1387394893-7789-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

On 12/19/13 08:28, Simon Paillard wrote:
> See http://bugs.debian.org/732464

Thanks. Applied.

Cheers,

Michael



> Reported-by: Raphael Geissert <geissert-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
> ---
>  man3/mcheck.3 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3/mcheck.3 b/man3/mcheck.3
> index 17b38cb..9c52a8e 100644
> --- a/man3/mcheck.3
> +++ b/man3/mcheck.3
> @@ -55,7 +55,7 @@ function must be called before the first call to
>  .BR malloc (3)
>  or a related function.
>  In cases where this is difficult to ensure, linking the program with
> -.IR \-mcheck
> +.IR \-lmcheck
>  inserts an implicit call to
>  .BR mcheck ()
>  (with a NULL argument)
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
--
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:[~2013-12-26 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 19:28 [PATCH] mcheck.3: typo in compiler flag Simon Paillard
     [not found] ` <1387394893-7789-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-12-26 18:28   ` 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=52BC7542.1000905@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=spaillard-8fiUuRrzOP0dnm+yROfE0A@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.