Duncan, I have fixed up the repo with git restore-mtime -- I think that should solve it - please check if it did what we needed.
Cheers, Simon > On Apr 3, 2024, at 2:41 AM, Duncan Murdoch <murdoch.dun...@gmail.com> wrote: > > On 02/04/2024 8:50 a.m., Dirk Eddelbuettel 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. > > Looks like those dates are gone -- the switch from svn to git involved some > copying, and I didn't preserve timestamps. > > I'll see about regenerating the more recent ones. I don't think there's much > historical interest in the pre-4.0 versions, so maybe I'll just nuke those. > > Duncan Murdoch > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
