From: Zefram <zefram@fysh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: ZSH workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: Not quite Re: info is rebuilt every time
Date: Wed, 5 Apr 2000 14:01:40 +0100 (BST) [thread overview]
Message-ID: <E12cpRE-0007pT-00@crucigera.fysh.org> (raw)
In-Reply-To: <1000405083226.ZM14407@candle.brasslantern.com> from Bart Schaefer at "Apr 5, 2000 08:32:26 am"
Bart Schaefer wrote:
>On the other hand, stamp-h.in always gets rebuilt for me, because I use
>a build dir separate from the source dir and the rules for the stamp-h.in
>target build $(sdir)/stamp-h.in rather than stamp-h.in, so ./stamp-h.in
>never gets any newer.
In this case, ./stamp-h.in shouldn't exist.
-zefram
next prev parent reply other threads:[~2000-04-05 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 6:55 Andrej Borsenkow
2000-04-05 8:32 ` PATCH: Not quite " Bart Schaefer
2000-04-05 8:42 ` Andrej Borsenkow
2000-04-05 13:01 ` Zefram [this message]
2000-04-05 14:51 ` Bart Schaefer
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=E12cpRE-0007pT-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).