From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Angelo Compagnucci <angelo@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] docs/website: fixing js for the new feed source
Date: Mon, 6 Feb 2023 11:02:10 +0100 [thread overview]
Message-ID: <20230206110210.235520f6@windsurf> (raw)
In-Reply-To: <20220925160320.80027-1-angelo@amarulasolutions.com>
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
>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
> ---
> docs/website/js/buildroot.js | 70 ++++++++++++++++++++----------------
> 1 file changed, 40 insertions(+), 30 deletions(-)
Finally applied, now that the cronjob is in place on the server! Thanks
a lot for your contribution and patience!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-02-06 10:02 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
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 [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=20230206110210.235520f6@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.