From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Worg updating?
Date: Thu, 17 Mar 2011 18:34:22 -0400 [thread overview]
Message-ID: <9834.1300401262@alphaville.usa.hp.com> (raw)
In-Reply-To: Your message of "Thu, 17 Mar 2011 10:53:47 -1000." <53412868-8EA9-445F-BFB0-FE7AFE6078B5@tsdye.com>
Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha all,
>
> Changes I made to the LaTeX export tutorial several days ago haven't
> made their way to Worg yet. Is Worg updating?
>
> All the best,
> Tom
>
Thanks for reminding me: I made a change to org-hacks some time ago and it
hasn't shown up yet. Maybe it would be a good idea to timestamp pages
with the update time?
Does Worg contain any information on how Worg is built? I found
http://orgmode.org/worg/sources/
but if those are the sources for the website, they are way out of date:
org-hacks.org has a date of 2011/03/03 but git log on my (recently
pulled) local repo shows many entries after that date. Since I pushed on
2011/03/04, I wonder if I am the one who broke it...
Nick
next prev parent reply other threads:[~2011-03-17 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 20:53 Worg updating? Thomas S. Dye
2011-03-17 22:34 ` Nick Dokos [this message]
2011-03-17 22:55 ` Erik Iverson
2011-03-18 2:54 ` Jason Dunsmore
2011-03-18 3:55 ` Nick Dokos
2011-03-18 4:56 ` Nick Dokos
2011-03-18 15:55 ` Thomas S. Dye
-- strict thread matches above, loose matches on Subject: below --
2010-09-17 16:32 Tom Dye
2010-09-17 17:10 ` John Hendy
2010-09-17 17:56 ` Erik Iverson
[not found] ` <87tylo2pnp.fsf@gmail.com>
2010-09-17 18:55 ` Bastien
2010-09-18 17:53 ` Bastien
2010-09-18 18:39 ` Tom Dye
2010-09-19 18:25 ` Bastien
2010-09-19 19:43 ` Tom Dye
2010-09-19 20:48 ` Bastien
2010-09-18 18:06 ` Bastien
2010-09-19 21:31 ` Bastien
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=9834.1300401262@alphaville.usa.hp.com \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).