emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: how to provide feedback to the org documentation on the website?
Date: Fri, 27 Sep 2013 23:31:58 -0400	[thread overview]
Message-ID: <87zjqxfwpd.fsf@gmail.com> (raw)
In-Reply-To: m11u494srx.fsf@poto.myhome.westell.com

tsd@tsdye.com (Thomas S. Dye) writes:
> Jason Lewis <jason@dickson.st> writes:
>> I noticed a word that is probably wrong in the org doco online. What's
>> the general procedure for providing feedback? It's not editable like a
>> wiki is it?
>>
>> Specifically on the page http://orgmode.org/manual/Beamer-export.html
>>
>> " Eventually, every plain list has support" should read "Finally, every
>> plain list has support"
>>
> It is editable! You can find how to register and use git for editing
> Worg here:
>
> http://orgmode.org/worg/worg-about.html
>
> It's actually a pleasure to work on its org-mode files.
>

That's true for worg files but Jason was talking about the org-mode
manual. I believe that's not editable except by developers. The easiest
way to make a change is to send a bug report. It's also possible to post
a patch to the list - in the same way that one would provide a patch for
code (with all the conditions that this implies: TINY change, FSF
copyright assignment, following conventions etc.). For details, see

         http://orgmode.org/worg/org-contribute.html

-- 
Nick

      reply	other threads:[~2013-09-28  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28  1:11 how to provide feedback to the org documentation on the website? Jason Lewis
2013-09-28  1:52 ` Thomas S. Dye
2013-09-28  3:31   ` Nick Dokos [this message]

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=87zjqxfwpd.fsf@gmail.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).