From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@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 1/4] Makefile: Don't leave $(GROFF_LOG) files behind
Date: Wed, 13 Apr 2016 19:28:10 -0400 [thread overview]
Message-ID: <20160413232810.GS6588@vapier.lan> (raw)
In-Reply-To: <20160414011304.289a6494.alex.miller-Mmb7MZpHnFY@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 287 bytes --]
On 14 Apr 2016 01:13, Alexander Miller wrote:
> Convert "GROFF_LOG" into a shell variable local to the
> recipe for "check-groff-warnings" target such that the
> temporary file is only created when needed.
Acked-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-13 23:28 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 [this message]
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 ` [PATCH 0/4] Makefile: fix temporary file handling and improve check-groff-warnings Michael Kerrisk (man-pages)
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=20160413232810.GS6588@vapier.lan \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=alex.miller-Mmb7MZpHnFY@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.