From: Andreas Schwab <schwab@linux-m68k.org>
To: ding@gnus.org
Subject: Re: one of my nntp servers won't open
Date: Tue, 28 Feb 2012 20:31:27 +0100 [thread overview]
Message-ID: <m28vjmbvqo.fsf@igel.home> (raw)
In-Reply-To: <pknk4367p4d.fsf@this.is.really.invalid> (Robert Pluim's message of "Tue, 28 Feb 2012 20:08:02 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> On Mon, 27 Feb 2012 22:31:04 +0100 Robert Pluim <rpluim@gmail.com> wrote:
>>
>> RP> This is with no-gnus. The server is always 'denied'
>> RP> Git bisect blames:
>>
>> RP> $ git show 9e4f0f845a97649bdeff35ef0356314d079a9383
>> RP> commit 9e4f0f845a97649bdeff35ef0356314d079a9383
>> RP> Author: Andreas Schwab <schwab@linux-m68k.org>
>> RP> Date: Sat Feb 25 13:18:09 2012 +0000
>>
>> RP> parse-time.el (parse-time-string): Allow extractor to return nil.
>>
>>
>> RP> What info from me would help here?
>>
>> Locally, do "git revert 9e4f0f845a97649bdeff35ef0356314d079a9383" and
>> see if that works (the revert could fail, you'd have to adjust the patch
>> then). Then you know for sure that this commit was the problem.
>
> I did
>
> git co c259392dfe4cb4c62b6ec388c384be8b55519214
>
> which should be the same
That's not the same. You are reverting _all_ later commits, whereas git
revert 9e4f0f only reverts a single commit.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-02-28 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 21:31 Robert Pluim
2012-02-27 23:23 ` Katsumi Yamaoka
2012-02-28 15:59 ` Ted Zlatanov
2012-02-28 19:08 ` Robert Pluim
2012-02-28 19:31 ` Andreas Schwab [this message]
2012-02-28 21:05 ` Robert Pluim
2012-02-29 15:13 ` 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=m28vjmbvqo.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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).