From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Subject: Re: backporting bugfixes to the v5-10 branch
Date: Wed, 23 Aug 2006 06:20:11 +0200 [thread overview]
Message-ID: <87zmdwrslg.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <v94pw427mr.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Tue, Aug 22 2006, Andreas Seltenreich wrote:
>
>> Andreas Seltenreich writes:
>>> Reiner Steib writes:
>>>> On Wed, Jul 12 2006, Andreas Seltenreich wrote:
>>>>
>>>>> I'm not sure what to do with the change to gnus-find-method-for-group:
>>>>>
>>>>> * gnus.el (gnus-find-method-for-group): On killed/unknown groups, try
>>>>> looking up the method using GROUP's prefix before inventing a new one.
>>>>> It is used on killed/unknown groups in various places where returning
>>>>> an all-new method isn't expected by the caller.
>>>>>
>>>>> While I can reproduce all of the bugs listed in
>>>>> <news:87fyhttsum.fsf@gate450.dyndns.org> on a stable Gnus,
>>>>
>>>> ... and the fix as well, I guess?
>>>
>>> Ack, I was unable to trigger the bugs anymore on v5-10 with the fix
>>> merged in.
>> [...]
>>> Btw, testing with the agent enabled revealed two places where
>>> g-f-m-f-g is called on groups after their prefix has been stripped,
>>> causing the native method to be returned. I don't think this is
>>> intentional, is it?
>>>
>>> [backtraces]
>
> Is this problem related to your change or not?
Negative, the new g-f-m-f-g doesn't change semantics in this case (no
prefix & no newsrc entry => primary method).
> Could you please summarize this problem again, Cc-ing Kevin Greiner
> and ask for his advise/opinion.
Will do so in a separate mail.
>> While I'm very confident that the change to g-f-m-f-g won't cause any
>> regressions, I do not /know/ that it won't. Especially with respect
>> to the agent.
>
> I don't have time to look at the code, but as the code is installed
> the trunk since 2006-06-25, it probably is sufficient testing (as the
> agent is enabled by default) by now to be installed in the trunk as
> well.
>
>> With Emacs pretest approaching, I'm still reluctant to commit it to
>> v5-10, and unless someone raises a more knowledgeable opinion, I'll
>> leave it on the trunk.
>
> After all, your changes fixed some problems still present in
> v5-10/Emacs CVS, so I'd say install it in v5-10 now.
Ok, I'll install it after some more testing.
regards,
andreas
next prev parent reply other threads:[~2006-08-23 4:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 22:24 Andreas Seltenreich
2006-07-17 17:52 ` Reiner Steib
2006-07-20 17:12 ` Andreas Seltenreich
2006-08-22 7:24 ` Andreas Seltenreich
2006-08-22 13:59 ` Reiner Steib
2006-08-23 4:20 ` Andreas Seltenreich [this message]
2006-08-23 7:20 ` The Agent vs. gnus-find-method-for-group (was: backporting bugfixes to the v5-10 branch) Andreas Seltenreich
2006-08-25 12:36 ` hook to insert sign command and forwarded messages gdt
2006-08-28 0:49 ` Katsumi Yamaoka
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=87zmdwrslg.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.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).