linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alexander Miller <alex.miller-Mmb7MZpHnFY@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/4] Makefile: fix temporary file handling and improve check-groff-warnings
Date: Mon, 18 Apr 2016 13:51:32 +0100	[thread overview]
Message-ID: <5714D854.3010404@gmail.com> (raw)
In-Reply-To: <20160414010434.1a7bdcfc.alex.miller-Mmb7MZpHnFY@public.gmane.org>

Hello Alex,

On 04/14/2016 12:04 AM, Alexander Miller wrote:
> Hello Michael,
> 
> a while ago I noticed that every time make is run a new empty file
> would be created in /tmp. This has been annoying me since, so I
> decided to have a look.
> 
> The first patch fixes this problem; the file is crated only for
> "make check-groff-warnings" where it is needed.
> While at it, I improved various bits for that target (in patch 2).
> Finally, the last 2 patches are purely cosmetic trivial changes.

I've applied all 4 patches. Thanks!

> I also noticed that check-groff-warnings works only with man-db.
> I happened to test it on a box with plain man and got a usage
> error for every man page. I haven't included a patch to silence
> these errors, since the old man has no equivalent for the --warnings
> option, and so I think it doesn't make sense to support it, you'd
> get the default warnings only. But if you like, I can provide a
> patch.

Best not to worry about it, I'd say.

Cheers,

Michael

> ---
> Alexander Miller (4):
>   Makefile: Don't leave $(GROFF_LOG) files behind
>   Makefile: Improve recipe for "check-groff-warnings" target
>   Makefile: wsfix (trailing space)
>   Makefile: Remove line continuation at end of "install" recipe
> 
>  Makefile | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 


-- 
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:[~2016-04-18 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 23:04 [PATCH 0/4] Makefile: fix temporary file handling and improve check-groff-warnings Alexander Miller
     [not found] ` <20160414010434.1a7bdcfc.alex.miller-Mmb7MZpHnFY@public.gmane.org>
2016-04-13 23:13   ` [PATCH 1/4] Makefile: Don't leave $(GROFF_LOG) files behind Alexander Miller
     [not found]     ` <20160414011304.289a6494.alex.miller-Mmb7MZpHnFY@public.gmane.org>
2016-04-13 23:28       ` Mike Frysinger
2016-04-13 23:16   ` [PATCH 2/4] Makefile: Improve recipe for "check-groff-warnings" target Alexander Miller
2016-04-13 23:17   ` [PATCH 3/4] Makefile: wsfix (trailing space) Alexander Miller
2016-04-13 23:18   ` [PATCH 4/4] Makefile: Remove line continuation at end of "install" recipe Alexander Miller
2016-04-18 12:51   ` 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=5714D854.3010404@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alex.miller-Mmb7MZpHnFY@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).