Many thanks Duncan,
I tried to look into the code but didn't manage to advance much due to some
java configuration issues.
To prevent being flooded by content of old versions I added a filter to
only repost those that the release version of the branch is in the title of
the content.
Maybe this would be helpful to avoid publishing the full NEWS again.
Lluís
On Tue, 2 Apr 2024 at 14:50, Dirk Eddelbuettel <e...@debian.org> wrote:
>
> On 2 April 2024 at 07:37, Dirk Eddelbuettel wrote:
> |
> | On 2 April 2024 at 08:21, Duncan Murdoch wrote:
> | | I have just added R-4-4-branch to the feeds. I think I've also fixed
> | | the \I issue, so today's news includes a long list of old changes.
> |
> | These feeds can fussy: looks like you triggered many updates. Feedly
> | currently greets me with 569 new posts (!!) in that channel.
>
> Now 745 -- and the bigger issue seems to be that the 'posted at' timestamp
> is
> wrong and 'current' so all the old posts are now seen as 'fresh'. Hence the
> flood ... of unsorted post.
>
> blosxom, simple as it is, takes (IIRC) filesystem ctime as the posting
> timestamp so would be best if you had a backup with the old timestamps.
>
> Dirk
>
> --
> dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
>
[[alternative HTML version deleted]]
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
