From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: cloudy Gnus
Date: Sun, 27 Mar 2011 20:35:20 +0200 [thread overview]
Message-ID: <87ipv49ztj.fsf@dod.no> (raw)
In-Reply-To: <87mxkga3n9.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> Ah, thanks. The .git/ORIG_HEAD contains 1a2936cbc8b4b584becd8426ac4959957e0595fd
> ie. this one
> http://git.gnus.org/cgit/gnus.git/commit/?id=1a2936cbc8b4b584becd8426ac4959957e0595fd
> Now I just need to find the energy to do a bisecting thing to see if I
> can find what commit changed the behaviour...:-)
Ok, done bisecting:
sb@aa1steinar:~/git/gnus$ git bisect good
f48235eacef5c56ad94704a17e438f9f6039ab71 is the first bad commit
commit f48235eacef5c56ad94704a17e438f9f6039ab71
Author: Ted Zlatanov <tzz@lifelogs.com>
Date: Fri Mar 11 13:39:30 2011 -0600
Adjust documentation and remove automatic read in hopes for Cloudy Gnus.
* gnus-sync.el (gnus-sync-install-hooks, gnus-sync-unload-hook): Don't
install `gnus-sync-read' to any hooks by default. It's buggy. The
user will have to run `gnus-sync-read' manually and wait for Cloudy
Gnus.
:040000 040000 6754ee1e53a386eb40a0c040b6c9ea79842b8f62 afd0a0c9b8e401ac728aadeff00140afa9645b49 M lisp
Ah... that explains it, I guess...?
next prev parent reply other threads:[~2011-03-27 18:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 12:21 nntp marks getting reset all the time Ted Zlatanov
2011-02-23 13:45 ` Steinar Bang
2011-02-23 14:32 ` Ted Zlatanov
2011-02-24 7:37 ` Steinar Bang
2011-02-24 16:31 ` Ted Zlatanov
2011-02-24 17:34 ` Steinar Bang
2011-02-24 17:47 ` cloudy Gnus (was: nntp marks getting reset all the time) Ted Zlatanov
2011-03-11 19:47 ` cloudy Gnus Ted Zlatanov
2011-03-15 15:54 ` Lars Magne Ingebrigtsen
2011-03-15 16:02 ` Ted Zlatanov
2011-03-15 16:11 ` Lars Magne Ingebrigtsen
2011-03-15 16:25 ` Ted Zlatanov
2011-03-15 16:33 ` Lars Magne Ingebrigtsen
2011-03-17 8:49 ` Steinar Bang
2011-03-15 16:59 ` Didier Verna
2011-03-15 17:02 ` Lars Magne Ingebrigtsen
2011-03-15 17:09 ` Adam Sjøgren
2011-03-15 17:21 ` Lars Magne Ingebrigtsen
2011-03-16 8:15 ` Didier Verna
2011-03-16 13:58 ` Ted Zlatanov
2011-03-16 17:30 ` Lars Magne Ingebrigtsen
2011-03-16 19:57 ` Frank Schmitt
2011-03-17 11:03 ` Didier Verna
2011-03-15 17:17 ` Ted Zlatanov
2011-03-15 17:23 ` Lars Magne Ingebrigtsen
2011-03-25 8:17 ` Steinar Bang
2011-03-25 19:31 ` Ted Zlatanov
2011-03-25 21:45 ` Steinar Bang
2011-03-26 20:53 ` Bernt Hansen
2011-03-27 17:12 ` Steinar Bang
2011-03-27 18:35 ` Steinar Bang [this message]
2011-02-25 3:01 ` nntp marks getting reset all the time Lars Ingebrigtsen
2011-02-25 14:45 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipv49ztj.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).