From: Suvayu Ali <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: Updating Worg: call to Worg authors
Date: Wed, 24 Apr 2013 09:52:14 +0200 [thread overview]
Message-ID: <20130424075214.GD28898@kuru.dyndns-at-home.com> (raw)
On Wed, Apr 24, 2013 at 09:44:32AM +0200, Bastien wrote:
> Suvayu Ali <firstname.lastname@example.org> writes:
> > I'm not clear about the workflow. Why is there a need for a separate
> > branch? I thought there was already a consensus to document the new
> > exporter under exporters/ox-<backend>.org or exporters/<exporter>/*.org
> > depending on whether a single file is sufficient or a directory is
> > needed for examples and other stuff. How does this new plan go with the
> > above, do I make changes in this new branch, or do I keep working on
> > master?
> There are two different things:
> - the exporters/ directory in Worg is for documenting how the new
> export engine and each exporter work
> - the new public branch is for updating Worg's pages so that the new
> exporter can publish them correctly (e.g., change the syntax of the
> #+attr_html lines, etc.)
> For adding new content to Worg (and for adding documentation to
> exporters/), just use Worg's master branch, as usual.
> For fixing the syntax of existing pages, go on the dedicated branch
> and do the fixes. We will merge this branch into master when it
> publishes fine with Org 8.0.
That clears it up :).
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-04-24 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 20:57 Jay Kerns
2013-04-24 7:25 ` Suvayu Ali
2013-04-24 7:44 ` Bastien
2013-04-24 7:52 ` Suvayu Ali [this message]
2013-04-24 7:53 ` Carsten Dominik
2013-04-24 9:25 ` Thorsten Jolitz
2013-04-25 23:18 ` Jay Kerns
2013-04-25 23:26 ` Jay Kerns
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).