Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Angelo Compagnucci <angelo@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] docs/website: fixing js for the new feed source
Date: Sun, 25 Sep 2022 21:41:43 +0200	[thread overview]
Message-ID: <20220925214143.05ba673a@windsurf> (raw)
In-Reply-To: <20220925160320.80027-1-angelo@amarulasolutions.com>

Hello Angelo,

On Sun, 25 Sep 2022 18:03:20 +0200
Angelo Compagnucci <angelo@amarulasolutions.com> wrote:

> Feed source is moved to a local atom file available on the web server to
> remove further problems with unreliable feed sources.
> Moving the feed required a bit of refactor of the load_activity function
> so it won't download two times te same url.
> 
> This change requires a cron job like this enabled on the website:
> * * * * * wget -O new.atom https://lore.kernel.org/buildroot/new.atom

Thanks a lot for working on this. Based on the cron job like that you
propose, I can see how this can fix the list of last e-mails on the
mailing list, but how can that fix the other box visible on the web
site, which lists the latest commits ?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-25 19:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 16:03 [Buildroot] [PATCH] docs/website: fixing js for the new feed source Angelo Compagnucci
2022-09-25 19:41 ` Thomas Petazzoni [this message]
2022-10-03 15:25   ` Angelo Compagnucci
2022-10-03 15:45     ` Thomas Petazzoni via buildroot
2023-02-06 10:02 ` Thomas Petazzoni via buildroot

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=20220925214143.05ba673a@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=angelo@amarulasolutions.com \
    --cc=buildroot@buildroot.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