From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org manual not updating when pulling from git
Date: Wed, 08 Feb 2017 00:01:08 +0100 [thread overview]
Message-ID: <84tw85hah7.fsf@tm6592> (raw)
In-Reply-To: 87k291loxf.fsf@Rainer.invalid
Hi!
Achim Gratz <Stromeko@nexgo.de> writes:
> Nick Dokos writes:
>> "make doc" or "make pdf" will update the PDF file. If you use one of
>> the update targets in the makefile, it may have been updating the pdf
>> doc under the covers. Taking a look through recent commits, the only one
>> that might be relevant seems to be this:
>>
>> ,----
>> | commit c90c7a33f53ad88dfcc583ad4c77bec306da0b22
>> | Author: Marco Wahl <marcowahlsoft@gmail.com>
>> | Date: Wed Feb 1 11:16:16 2017 +0100
>> |
>> | targets.mk: Drop the rule to clean at every compile
>> |
>> | Rationale: 1. Save time and energy. 2. Use the make tool for what
>> | it's been made.
>> `----
>
> That commit should probably be reverted. The make tool can't do what
> it's been made for in this case since some of the dependencies can not
> be correctly determined. You can still skip the clean if you want to by
> using the compile-dirty target.
Ah! I didn't see target 'compile-dirty'. Thank you for the hint.
So for now I'm happy with the build process with the existence of
make compile-dirty
and further
make test-dirty
Also the names are well chosen AFAICT.
I agree that the commit should be reverted and I already did the revert.
Please accept my apology for the irritation about the build behavior.
Best regards
Marco
next prev parent reply other threads:[~2017-02-07 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 18:38 org manual not updating when pulling from git Charles Millar
2017-02-07 19:41 ` Nick Dokos
2017-02-07 20:35 ` Achim Gratz
2017-02-07 23:01 ` Marco Wahl [this message]
2017-02-08 18:43 ` Achim Gratz
2017-02-07 23:59 ` Charles Millar
2017-02-08 16:39 ` Nick Dokos
2017-02-08 16:54 ` Charles Millar
2017-02-08 18:35 ` Marco Wahl
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84tw85hah7.fsf@tm6592 \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).