emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Gregory Benjamin <gregb@laserlab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: editing "The compact Org-Mode Guide"
Date: Tue, 05 Feb 2013 20:49:51 +0100	[thread overview]
Message-ID: <87a9riwnfk.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20130205184331.GB4740@dbn66.laserlab.com> (Gregory Benjamin's message of "Tue, 5 Feb 2013 10:43:31 -0800")

Hi Gregory,

Gregory Benjamin <gregb@laserlab.com> writes:

> I started reading "orgguide.pdf", Release 7.9.3e and came across a
> couple of grammatical errors right away.
>
> 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.

thanks in advance for this work!

Thomas gave all information you need to start -- one correction:
orgguide.texi is not part of Emacs, so you don't need to assign
your copyright to the FSF for them.

Another caveat: most of orgguide.texi comes from org.texi, so
it is very like that, if you find a typo in orgguide.texi, the 
typo will be in org.texi too.  If you want to provide a patch
for org.texi too, then you'll have to assign your copyright
to the FSF -- or to let Thomas or/and I backport your changes
into org.texi.

All best,

-- 
 Bastien

  parent reply	other threads:[~2013-02-05 19:49 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
2013-02-07  9:01     ` Bastien
2013-02-05 19:49 ` Bastien [this message]
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=87a9riwnfk.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=gregb@laserlab.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).