From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2] docs: make .txt files over-writable when building from r/o sources
Date: Fri, 25 Jul 2014 16:24:56 +0100 [thread overview]
Message-ID: <53D276C8.50303@citrix.com> (raw)
In-Reply-To: <53D28C43020000780002613A@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 660 bytes --]
On 25/07/14 15:56, Jan Beulich wrote:
> Otherwise an incremental build will fail to overwrite the destination
> files.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> v2: Use $(INSTALL_DATA) instead of cp+chmod.
>
> --- a/docs/Makefile
> +++ b/docs/Makefile
> @@ -124,7 +124,7 @@ endif
>
> html/%.txt: %.txt
> $(INSTALL_DIR) $(@D)
> - cp $< $@
> + $(INSTALL_DATA) $< $@
>
> html/man/%.1.html: man/%.pod.1 Makefile
> $(INSTALL_DIR) $(@D)
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 1554 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-07-25 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:43 [PATCH] docs: make .txt files writable when building from r/o sources Jan Beulich
2014-07-04 14:47 ` Andrew Cooper
2014-07-04 14:51 ` Jan Beulich
2014-07-04 15:04 ` Andrew Cooper
2014-07-25 14:56 ` [PATCH v2] docs: make .txt files over-writable " Jan Beulich
2014-07-25 15:24 ` Andrew Cooper [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=53D276C8.50303@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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.