emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Evan Misshula <evanmisshula@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: editing "The compact Org-Mode Guide"
Date: Tue, 5 Feb 2013 14:22:24 -0500	[thread overview]
Message-ID: <CAPV3ZjzyGYRuQzAkbk8SJLLF7c8dr=jC+i7uRfDmj0Y1HXXKRA@mail.gmail.com> (raw)
In-Reply-To: <m1wqumlgoi.fsf@poto.myhome.westell.com>

Thanks for the instructions on how to play nice in the sandbox.  We
noobs are always afraid
we are going to cause more work than we fix.

:-)

On Tue, Feb 5, 2013 at 2:11 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Greg,
> Gregory Benjamin <gregb@laserlab.com> writes:
>
>> I'd like to take a stab at making some corrections and would like to
>> have access to the source for this document. With some guidance, I
>> should be able to produce a patch that can be incorporated into the
>> next realease.
>
> The source is /path/to/org-mode/doc/orgguide.texi
>
> There is a file in that directory called Documentation_Standards.org,
> which contains what the file name advertises.
>
>>
>> Please provide me with instructions on downloading the source, and
>> after I finish editing, uploading the diffs or updated version.
>
> Assuming you are using the git version of Org mode, you should create a
> new branch, check it out, and edit orgguide.texi there.
>
> When you are happy with your edits, stage and commit them in the git
> repository.  Once the edits have been committed, you can make a patch like
> this:
>
> git format-patch -o ~/temp/ HEAD~1
>
> where ~/temp/ is what I use and might not be appropriate for your setup,
> so should be changed accordingly.
>
> You should read the instructions on formatting patches here:
>
> http://orgmode.org/worg/org-contribute.html#sec-4
>
> It saves the developers a lot of time if you follow these instructions.
>
> Finally, if you're likely to go over the limits of a TINY CHANGE, then
> you will want to assign your work to FSF so that it can be included in
> Emacs.  See the instructions here:
>
> http://orgmode.org/worg/org-contribute.html#sec-2
>
> Hopefully, I've remembered all the steps. If this doesn't work for you,
> come back to the list with queries.
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>



-- 
Evan Misshula
Doctoral Student (Criminal Justice)
CUNY John Jay
"Let us reform our schools, and we shall find little reform needed in
our prisons."
       John Ruskin, Unto This Last, essay 2 (1862)
       English critic, essayist, & reformer (1819 - 1900)

"Instruction does much, but encouragement does everything." Johann
Wolfgang Von Goethe
www.snrg-nyc.org

  reply	other threads:[~2013-02-05 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 18:43 editing "The compact Org-Mode Guide" Gregory Benjamin
2013-02-05 19:11 ` Thomas S. Dye
2013-02-05 19:22   ` Evan Misshula [this message]
2013-02-07  9:01     ` Bastien
2013-02-05 19:49 ` Bastien
2013-02-13 19:19 ` segfault on 'make test' Gregory Benjamin
2013-02-13 19:59   ` Bastien
2013-02-13 20:33   ` Achim Gratz
2013-03-11 19:26   ` Agenda buffer behavior Gregory Benjamin
2013-03-11 22:06     ` Marcin Borkowski
2013-03-12  1:29     ` Eric Abrahamsen

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='CAPV3ZjzyGYRuQzAkbk8SJLLF7c8dr=jC+i7uRfDmj0Y1HXXKRA@mail.gmail.com' \
    --to=evanmisshula@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).