Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: generated dates should not be hashed (was: duplicate items in nnrss groups)
Date: Sat, 16 Sep 2006 15:54:28 +0200	[thread overview]
Message-ID: <9eu0379asr.fsf_-_@doze.jochen-kuepper.de> (raw)
In-Reply-To: <9e64fo9d7v.fsf-X+QEHg5KIgm/8B4OpmtwqPxnRIzENc/G@public.gmane.org> (Jochen =?iso-8859-1?Q?K=FCpper's?= message of "Sat\, 16 Sep 2006 15\:02\:12 +0200")

Ok, I think I have spotted the problem with the duplicate entries I
encounter in nnrss feeds:

For the feeds without a date specified, in nnrss-normalize-date the
,----
|     (cond ((null date))
`----
case is true. Therefore, at the end of that function 
,----
| message-make-date
`----
is called to create a valid date. Therefore, every time when running
nnrss-check-group the current date is used. On successive hashing of
the item, it is changed form the last update due to the new date.

Therefore I would suggest that the date should not be used in creating
the item hash, or at least it should be configurable to do so.

Or is there a better way of dealing with the problem?

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)



      parent reply	other threads:[~2006-09-16 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 20:25 duplicate items in nnrss groups Jochen Küpper
2006-09-10 21:48 ` David Hansen
     [not found]   ` <87slizbdgb.fsf-/PVU1wbgskXSxOb6xA1WPVLmfr9GSJok@public.gmane.org>
2006-09-11  8:07     ` Jochen Küpper
2006-09-14 16:51   ` Mark Plaksin
     [not found]     ` <wszmd2xuh3.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-14 19:40       ` Jochen Küpper
2006-09-14 20:50         ` Mark Plaksin
     [not found]           ` <wsejuexjds.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-14 21:34             ` Jochen Küpper
2006-09-15 16:12               ` Mark Plaksin
     [not found]                 ` <wsmz91un18.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-16 13:02                   ` Jochen Küpper
     [not found]                     ` <9e64fo9d7v.fsf-X+QEHg5KIgm/8B4OpmtwqPxnRIzENc/G@public.gmane.org>
2006-09-16 13:54                       ` Jochen Küpper [this message]

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=9eu0379asr.fsf_-_@doze.jochen-kuepper.de \
    --to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).