Re: [O] small docstring typo in org-clone-subtree-with-time-shift

2011-09-30 Thread Brian van den Broek 
On 29 Sep 2011 23:17, Achim Gratz strom...@nexgo.de wrote:

 Brian van den Broek brian.van.den.br...@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

snip patient and thorough seeming explanation

 Check How to contribute to Orgmode on the website.


 HTH,
 Achim.

Hi Achim,

Thanks for that, especially in a context where an RTFM would not have been
unwarranted.

As it happens, I've set aside some time for a pass through the manual in the
next while (for me, this is a semi-annual affair) and I pledge to repay your
kindness in providing these step by step instructions by making active use
of them!

Thanks again,

Brian vdB

[O] small docstring typo in org-clone-subtree-with-time-shift

2011-09-29 Thread Brian van den Broek 
Hi all,

First, I've not been active on the list for some lengthy time. When
last I was reporting small typos in the manual, Cartsen was still the
chief maintainer and I just sent them to him directly. Please advise
as to where such trivial doc bugs are best noted.

Second, the docstring for org-clone-subtree-with-time-shift contains
the phrase `I this way you can spell out a number of instances of a
repeating task,'. Clearly, `I' ought be `In'.

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.

Thanks and best,

Brian vdB

Re: [O] small docstring typo in org-clone-subtree-with-time-shift

2011-09-29 Thread Achim Gratz 
Brian van den Broek brian.van.den.br...@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.


HTH,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds