Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Merging nnweb.el changes to v5-10?
Date: Tue, 02 Jan 2007 01:56:45 +0100	[thread overview]
Message-ID: <87ejqemek2.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <v9y7omcqdn.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 01 Jan 2007 23\:51\:32 +0100")

Reiner Steib writes:

> could someone please merge the recent nnweb.el changes to v5-10 if
> appropriate (Andreas maybe?)?

I'm currently waiting for the next update of the Xapian index to see
if the solid nnweb groups I created for testing update properly.

> I.e. are these change bug fixes that should be included in v5-10?

I think so.  nnweb is supposed to keep the article numbers stable for
solid groups, even when successive searches return a different set of
articles, or return them in a different order.

This broke with my revision of the code for nov.php, because I wasn't
updating the article numbers of the headers read from nov.php to the
ones computed by nnweb before passing the headers to Gnus.  The
problem wasn't apparent, since the article numbers returned by nov.php
/usually/ matched those generated by nnweb.

The code on the trunk now consistently uses the numbers generated by
nnweb.  I just reverted a change by Lars that I /think/ was part of
his first approach at fixing it by consistently using the article
numbers from nov.php.

So, if Lars doesn't veto, and the testing turns out positive, I'll put
nnweb.el of the trunk (minus the TOPDOC-change) on the v5-10 branch.

regards,
andreas



  reply	other threads:[~2007-01-02  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 22:51 Reiner Steib
2007-01-02  0:56 ` Andreas Seltenreich [this message]
2007-01-03 20:52   ` Andreas Seltenreich
2007-01-03 21:20   ` Reiner Steib

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=87ejqemek2.fsf@gate450.dyndns.org \
    --to=andreas+ding@gate450.dyndns.org \
    --cc=larsi@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).