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, 3 Oct 2022 17:45:35 +0200 [thread overview]
Message-ID: <20221003174535.12946beb@windsurf> (raw)
In-Reply-To: <CA+_SqVbs4_tPr4y9kMCP0f9dsjxO5bX48zvz45ABynfpbVzaEA@mail.gmail.com>
On Mon, 3 Oct 2022 17:25:18 +0200
Angelo Compagnucci <angelo@amarulasolutions.com> wrote:
> > 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 ?
>
> This feed mixes commit/non commit entries, so the choice on which box fill
> up is in the js code.
Aaah, it uses the git commit notifications available in the mailing
list. Smart thing!
Thanks for this contribution. We'll have a look at setting it up, with
the cronjob that it requires.
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
next prev parent reply other threads:[~2022-10-03 15:45 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 [this message]
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=20221003174535.12946beb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox