From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: small docstring typo in org-clone-subtree-with-time-shift Date: Thu, 29 Sep 2011 22:16:32 +0200 Message-ID: <87y5x73xzz.fsf@Rainer.invalid> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:60621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R9N2R-0005l5-HY for emacs-orgmode@gnu.org; Thu, 29 Sep 2011 16:17:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R9N2G-0003Vf-KM for emacs-orgmode@gnu.org; Thu, 29 Sep 2011 16:16:59 -0400 Received: from lo.gmane.org ([80.91.229.12]:40176) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R9N2G-0003VG-FF for emacs-orgmode@gnu.org; Thu, 29 Sep 2011 16:16:48 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9N2E-00089y-Rt for emacs-orgmode@gnu.org; Thu, 29 Sep 2011 22:16:46 +0200 Received: from p57aadcdd.dip.t-dialin.net ([87.170.220.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 22:16:46 +0200 Received: from Stromeko by p57aadcdd.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 22:16:46 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Brian van den Broek 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