emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Worg publishing issue
Date: Sat, 09 Feb 2013 00:35:24 +0100	[thread overview]
Message-ID: <87bobunzur.fsf@gmail.com> (raw)
In-Reply-To: 20130208225437.GC4223@kuru.dyndns-at-home.com

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> I still see issues with the publishing.  My previous commit[1] to the FAQ
> was not published.  

I actually looked up the link after your post and everything looked
fine. 

> The post-commit hook output had timed out on my end
> then.  I had thought that was probably some network issue on my side but
> that doesn't seem to be the case.  When I tried to push some more edits[2]
> to that entry, I see the following message
>
> remote: Worg publish process 11929 is still running...
>
> Can someone please take a look?

I just looked up your second link, and everything looks fine again, here
is the unformatted version of what I see:

,------------------------------------------------------------------------------------------
| cgit logo       index : worg.git        
| Org community-driven documentation and code snippets    
| summaryrefslogtreecommitdiff    
| diff options
| context:        
| space:  
| mode:   
|         
| author  Suvayu Ali <fatkasuvayu+linux@gmail.com>        2013-02-08 22:48:12 (GMT)
| committer       Suvayu Ali <fatkasuvayu+linux@gmail.com>        2013-02-08 22:48:12 (GMT)
| commit  12fadc1554816ecd21fddc0af589070a99e94245 (patch)
| tree    7fe71f08c39d9dbb6c2ab3b6fbc264d7d66f12b0
| parent  e6a51c5a553d6ab4d164af7d1ce54fbc5b5028a0 (diff)
| download        worg-12fadc1554816ecd21fddc0af589070a99e94245.zip
| worg-12fadc1554816ecd21fddc0af589070a99e94245.tar.gz
| Update new exporter switch FAQHEADmaster
| Diffstat
| -rw-r--r--      org-faq.org     14      
|                 
| 1 files changed, 9 insertions, 5 deletions
| diff --git a/org-faq.org b/org-faq.org
| index 9df7818..7ea4087 100644
| --- a/org-faq.org
| +++ b/org-faq.org
| @@ -316,15 +316,19 @@ about the number of list readers.
| Some quick notes on how to switch to the new exporter.
| -1. Export engine renamed: org-export → ox
| -2. Backend requires renamed: org-e-* → ox-*
| -3. All backend specific variables and functions renamed:
| +1. If you had already been using the new exporter from contrib, you
| + should remove the following lines from your local.mk:
| + : ORG_ADD_CONTRIB = org-e-*
| + followed by a =make clean=, before you do =git pull=.
| +2. Export engine renamed: org-export → ox
| +3. Backend requires renamed: org-e-* → ox-*
| +4. All backend specific variables and functions renamed:
| - org-export-* → org-* (e.g. org-html-xml-declaration, ..)
| - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets, ..)
| -4. Generic export variables retain the name org-export-*
| +5. Generic export variables retain the name org-export-*
| (e.g. org-export-dispatch-use-expert-ui,
| org-export-filter-headline-functions, ..)
| -5. org-latex-to-pdf-process has been renamed to org-latex-pdf-process
| +6. org-latex-to-pdf-process has been renamed to org-latex-pdf-process
| 7. This is a guess, export snippets and backend symbols renamed:
| - e-<backend> → <backend>
| generated by cgit v0.9.0.3-65-g4555 at 2013-02-08 23:32:04 (GMT)
`------------------------------------------------------------------------------------------

> [2] <http://orgmode.org/cgit.cgi/worg.git/commit/?id=12fadc1554816ecd21fddc0af589070a99e94245>

-- 
cheers,
Thorsten

  reply	other threads:[~2013-02-08 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 13:19 Worg publishing issue Suvayu Ali
2013-02-06 15:26 ` Nick Dokos
2013-02-07  8:42 ` Bastien
2013-02-07  9:35   ` Suvayu Ali
2013-02-13 17:32     ` Bastien
2013-02-13 19:37       ` Suvayu Ali
2013-02-07 12:43   ` Nicolas Goaziou
2013-02-13 10:45     ` Bastien
2013-02-08 22:54 ` Suvayu Ali
2013-02-08 23:35   ` Thorsten Jolitz [this message]
2013-02-08 23:39   ` Thorsten Jolitz

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=87bobunzur.fsf@gmail.com \
    --to=tjolitz@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).