From: Bernt Hansen <bernt@norang.ca>
To: Melton Low <softw.app@gmail.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Org-mode version 6.30d; Hide stars
Date: Fri, 04 Sep 2009 14:33:21 -0400 [thread overview]
Message-ID: <873a72imq6.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <23d923960909041005j221dec97k69cbefad0667a57d@mail.gmail.com> (Melton Low's message of "Fri\, 4 Sep 2009 11\:05\:20 -0600")
Melton Low <softw.app@gmail.com> 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
next prev parent reply other threads:[~2009-09-04 18:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 14:44 Org-mode version 6.30d; Hide stars Melton Low
2009-09-04 15:07 ` Carsten Dominik
2009-09-04 17:05 ` Melton Low
2009-09-04 18:33 ` Bernt Hansen [this message]
2009-09-04 19:00 ` William Henney
2009-09-04 19:26 ` Bernt Hansen
2009-09-04 20:56 ` Mark Elston
2009-09-04 21:36 ` Arne
2009-09-05 5:42 ` Carsten Dominik
2009-09-05 5:58 ` Carsten Dominik
2009-09-05 9:44 ` Detlef Steuer
2009-09-05 14:23 ` Melton Low
[not found] <cmu-lmtpd-24989-1252080523-5@store70m.internal>
2009-09-04 16:26 ` Scott Otterson
2009-09-06 17:47 ` Tassilo Horn
2009-09-06 22:32 ` Melton Low
2009-09-06 22:40 ` Melton Low
2009-09-07 8:35 ` Tassilo Horn
2009-09-07 18:04 ` Tassilo Horn
2009-09-07 18:17 ` Mark Elston
2009-09-07 18:32 ` Tassilo Horn
2009-09-07 21:50 ` Melton Low
2009-09-08 7:47 ` Tassilo Horn
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 5:20 Melton Low
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=873a72imq6.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=softw.app@gmail.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).