emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org manual not updating when pulling from git
Date: Tue, 07 Feb 2017 14:41:58 -0500	[thread overview]
Message-ID: <87shnpokjd.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 184df969-a0ea-ee74-1b1d-21691634590c@verizon.net

Charles Millar <millarc@verizon.net> writes:

> When pulling from git, shouldn't the manual be updated if for no other
> reason than to refelct the most recent org version?
>

It depends on what you mean by "the manual" - the texinfo source is updated,
but any derived files (info, pdf) are not: they are not under source control
at all.

> Up unitl two or three days ago, this was my experience. Now, however,
> none of the documentation seems to be updating, e g.
>
> current Org mode version 9.0.4 (release_9.0.4-283-g2064b0 @
> /usr/local/share/emacs/site-lisp/org-mode/lisp/)
>
> pdf manual shows version Release 9.0.4 (release 9.0.4-263-gf15728)
>

"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.
`----

So, how do you update?

-- 
Nick

  reply	other threads:[~2017-02-07 19:42 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 [this message]
2017-02-07 20:35   ` Achim Gratz
2017-02-07 23:01     ` Marco Wahl
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=87shnpokjd.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@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).