public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/6] website/sponsors.html: remove sense
Date: Wed, 25 Mar 2026 11:19:04 +0100	[thread overview]
Message-ID: <20260325101904.79397-1-thomas.perale@mind.be> (raw)
In-Reply-To: <70855a978c2bf9c568f6bc6cdb033c3b@free.fr>

Hi Julien,

> Instead of removing the sponsor, could you instead move it
> to the "Past Sponsors" section, and add the mention it was
> a LTS sponsor?

Thanks for the comment, I moved 'Sense' to past sponsor in my new series but
had to modify the css of the 'sponsors.html' page to make the "stack" easy to
work with in the future.

Best regards,
PERALE Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-03-25 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 15:02 [Buildroot] [PATCH 1/6] website/sponsors.html: remove sense Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 2/6] website/sponsors.html: add IPComm as a silver sponsor Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 3/6] website/lts: remove the href on section Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 4/6] website/lts: fix section on small screens Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 5/6] website/lts: add pre-filled content to mailto Thomas Perale via buildroot
2026-03-19 15:02 ` [Buildroot] [PATCH 6/6] website/lts: fix typos Thomas Perale via buildroot
2026-03-24 21:27 ` [Buildroot] [PATCH 1/6] website/sponsors.html: remove sense Julien Olivain via buildroot
2026-03-25 10:19   ` Thomas Perale 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=20260325101904.79397-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.perale@mind.be \
    /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