emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: small docstring typo in org-clone-subtree-with-time-shift
Date: Thu, 29 Sep 2011 22:16:32 +0200	[thread overview]
Message-ID: <87y5x73xzz.fsf@Rainer.invalid> (raw)
In-Reply-To: CAF6DajLzVMOAPTO3S7p23RZ3JjfBKQ9GyybjzhteGffQUYwjVg@mail.gmail.com

Brian van den Broek <brian.van.den.broek@gmail.com> writes:
> I suspect that the optimal way is to generate a patch against the
> documentation. If that's right and someone would point me to what I'd
> need to read to learn how to do so (I've never produced a patch
> before), I'd be happy to learn and do it that way henceforward.

Make your own clone of the Git repository.  Check out the master branch
and make a new branch for the patch.  Edit the file(s) that you want to
patch and commit that change with a commit message that has an
appropriate ChangeLog entry.  Create a patch file and attach it to a
post to this list with [PATCH] in the subject line.  Maybe give a bit of
an explanation that didn't make it into the commit message if you feel
that may be necessary.  Do not make unrelated changes in the same
commit, rather have these in separate commits.

git checkout master
git branch patch
git commit -a
git format-patch

Check "How to contribute to Orgmode" on the website.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:

  reply	other threads:[~2011-09-29 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 12:06 small docstring typo in org-clone-subtree-with-time-shift Brian van den Broek
2011-09-29 20:16 ` Achim Gratz [this message]
2011-09-30  8:43   ` Brian van den Broek

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:

  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=87y5x73xzz.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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).