From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/Makefile: remove cmd-list.made before redirecting to it.
Date: Mon, 06 Aug 2007 23:33:42 -0700 [thread overview]
Message-ID: <7vlkcn97ll.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86vebsby27.fsf@lola.quinscape.zz> (David Kastrup's message of "Mon, 6 Aug 2007 15:05:56 +0200")
David Kastrup <dak@gnu.org> writes:
> If cmd-list.made has been created by a previous run as root, output
> redirection to it will fail. So remove it before regeneration.
>
> Signed-off-by: David Kastrup <dak@gnu.org>
> ---
> Documentation/Makefile | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/Makefile b/Documentation/Makefile
> index 97ee067..120e7c0 100644
> --- a/Documentation/Makefile
> +++ b/Documentation/Makefile
> @@ -120,6 +120,7 @@ $(cmds_txt): cmd-list.made
>
> cmd-list.made: cmd-list.perl $(MAN1_TXT)
> perl ./cmd-list.perl
> + $(RM) $@
> date >$@
>
> git.7 git.html: git.txt core-intro.txt
Although I understand that it would be a problem if you built as
root earlier, which would have left files unmodifyable by you, I
think this is getting out of hand. The cmd-list.perl script
itself, for example, does "creat in $out+, if the contents have
changed from the last round then rename $out+ to $out" sequence
in order to avoid unnecessary rebuild of files that depend on
the generated command list. If it is interrupted in the middle
while running as root, and then you try to do another build, I
suspect "creat in $out+" part would fail.
Maybe you can simply recover from such an error with a "make
clean"?
Also I'd prefer $(RM) before actually running the command to
generate the list, but that is just the matter of taste.
next prev parent reply other threads:[~2007-08-07 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 13:05 [PATCH] Documentation/Makefile: remove cmd-list.made before redirecting to it David Kastrup
2007-08-07 6:33 ` Junio C Hamano [this message]
2007-08-07 10:29 ` David Kastrup
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=7vlkcn97ll.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.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