From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Org-mode version 6.30d; Hide stars Date: Fri, 04 Sep 2009 14:33:21 -0400 Message-ID: <873a72imq6.fsf@gollum.intra.norang.ca> References: <23d923960909040744v616a7503uc1ceb32dcb57eba2@mail.gmail.com> <07374B44-6A29-46C3-96C4-0EE89D8D05E7@gmail.com> <23d923960909041005j221dec97k69cbefad0667a57d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MjdbH-0006i1-QK for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 14:33:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MjdbE-0006aX-8B for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 14:33:31 -0400 Received: from [199.232.76.173] (port=60428 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MjdbE-0006aS-1B for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 14:33:28 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:50039) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MjdbD-0005Xn-OI for emacs-orgmode@gnu.org; Fri, 04 Sep 2009 14:33:27 -0400 In-Reply-To: <23d923960909041005j221dec97k69cbefad0667a57d@mail.gmail.com> (Melton Low's message of "Fri\, 4 Sep 2009 11\:05\:20 -0600") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Melton Low Cc: emacs-orgmode@gnu.org, Carsten Dominik Melton Low writes: > When I get a chance later today or this evening, I will try to > identify which git commit the problem started for me. For that you want to use 'git bisect' You identify a commit that is bad (probably master) and a commit that is good (some previous commit) and do something like $ git bisect start $BAD $GOOD (ie git bisect start master master~20 -- where master is bad (showing the problem) and master~20 is a previous commit that does not have the problem. You can identify the commits by SHA1, or as an ancestor of some branch tip) git will do a binary search of the commits and checkout a commit between $BAD and $GOOD for you to test. I normally reload the org files from source with C-u M-x org-reload and then redo my test for each of the checkouts that git bisect picks. If your test fails you do $ git bisect bad and if it passes you do $ git bisect good then git checks out a new commit for you to test. This identifies the bad commit very quickly. It is also possible to automate this procedure if you can provide a script that can test the checked out version for success or failure and return a status of 0 or 1 appropriately. See the git bisect man page for more details. HTH, Bernt