From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80726 Path: news.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: TIP: using git-bisect (Was: nnimap no workee once again) Date: Tue, 03 Jan 2012 08:39:45 +0100 Organization: Probably a good idea Message-ID: <8739bxqloe.fsf_-_@dod.no> References: <878vlq15uq.fsf@newsguy.com> <87obumqefo.fsf@dod.no> <87d3b1sr1i.fsf@newsguy.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1325576415 11820 80.91.229.12 (3 Jan 2012 07:40:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 3 Jan 2012 07:40:15 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M29008@lists.math.uh.edu Tue Jan 03 08:40:11 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Rhyyh-00018X-0D for ding-account@gmane.org; Tue, 03 Jan 2012 08:40:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Rhyye-0001Rq-24; Tue, 03 Jan 2012 01:40:08 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Rhyyd-0001Rj-34 for ding@lists.math.uh.edu; Tue, 03 Jan 2012 01:40:07 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1Rhyya-0000w2-Q9 for ding@lists.math.uh.edu; Tue, 03 Jan 2012 01:40:06 -0600 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1RhyyY-0003sy-0G for ding@gnus.org; Tue, 03 Jan 2012 08:40:02 +0100 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RhyyX-00015u-TV for ding@gnus.org; Tue, 03 Jan 2012 08:40:01 +0100 Original-Received: from cm-84.208.231.161.getinternet.no ([84.208.231.161]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jan 2012 08:40:01 +0100 Original-Received: from sb by cm-84.208.231.161.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jan 2012 08:40:01 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 45 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cm-84.208.231.161.getinternet.no Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:257Af46/JNmE0/ek6lSjn2/bZJE= X-Spam-Score: -6.2 (------) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80726 Archived-At: >>>>> Harry Putnam : > Steinar Bang writes: >> Have you tried using git bisect to narrow it down to a specific commit? > I've never bisected a git... I Disected a few frogs once : ) Googling for git-bisect should give you the docs http://book.git-scm.com/5_finding_issues_-_git_bisect.html > Honestly I have no idea what you are talking about... but it did get > me thinking to update gnus and see if the problem persists. Ok. Sounds like the not working didn't come because of a "git pull"...? If so, it's a good idea to say so. It narrows down the possibilities. Using git bisect applies when a "git pull" leaves you with a broken gnus. What I do in that case, is: 1. Find the SHA1 from before the last pull (the contents of .git/ORIG_HEAD), this will be "good" 2. Start the command git bisect start bad good where bad is a sha1 hash, or tag, that you know is bad, eg. HEAD and good is a sha1 hash, or tag, that you know is good. If I've done nothing except pulling from upstream in my repo, and the previous version was ok, I can actually do this git bisect start HEAD ORIG_HEAD then you loop, doing this: a. do "make clean" followed by "make" (or "./configure && make" if that's your preference) b. start a new emacs and start gnus and see if the problem persist. If the problem persists, do git bisect bad If the problem isn't there, do git bisect good If "git bisect" tells me that it has found the first offending commit, then go to 3, else go to a. 3. Copy the text from "git bisect" where it found the offending commit, and send it to the gnus group 4. Use "git bisect reset" to set the working directory back to normal, then decide if I want to try to fix the issue yourself, or pull back to the last good version, until it can be fixed, and then "make clean" and "make" gnus