From: David Maus <dmaus@ictsoc.de>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-publish not publishing changed files
Date: Sun, 20 Mar 2011 12:30:32 +0100 [thread overview]
Message-ID: <87oc5658rr.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <20110318191950.32fdee41@bhishma.homelinux.net>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
At Fri, 18 Mar 2011 19:19:50 -0700,
Suvayu Ali wrote:
>
> On Fri, 18 Mar 2011 21:33:04 -0400
> Nick Dokos <nicholas.dokos@hp.com> wrote:
>
> > If you can figure out *why* they got out of sync, that would be
> > a bonus and worth a post here, particularly if you can identify
> > a bug in the code.
>
> I think there was a post sometime earlier where the OP faced this issue
> because his setup used symlinks. The timestamps of the symlinks didn't
> change so the publishing didn't happen.
The issue with publishing symlinked files was fixed in Januar by
b4979a86ca10d058a780440e88c5a3e33c1adff5.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-03-20 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 9:08 Override export filename Aidan Gauland
2010-11-02 15:44 ` Giovanni Ridolfi
2010-11-02 18:04 ` Aidan Gauland
[not found] ` <aidalgol@no8wireless.co.nz>
2010-11-02 18:35 ` Nick Dokos
2010-11-05 0:57 ` Aidan Gauland
2011-03-19 1:33 ` org-publish not publishing changed files Nick Dokos
2011-03-19 2:19 ` Suvayu Ali
2011-03-20 11:30 ` David Maus [this message]
2011-03-20 11:47 ` Suvayu Ali
2011-03-22 2:00 ` Aidan Gauland
2011-03-22 6:18 ` Nick Dokos
2011-03-22 7:32 ` Aidan Gauland
2011-03-22 14:17 ` Nick Dokos
2011-04-01 19:56 ` Aidan Gauland
-- strict thread matches above, loose matches on Subject: below --
2011-03-19 1:16 Aidan Gauland
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=87oc5658rr.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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).