Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/harfbuzz: bump version to 8.1.0
Date: Fri, 4 Aug 2023 22:28:46 +0200	[thread overview]
Message-ID: <20230804222846.0d1b93c7@windsurf> (raw)
In-Reply-To: <c5722386-f614-e42e-72e0-79728276fa42@benettiengineering.com>

On Fri, 4 Aug 2023 22:25:38 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> Yes, I've already done it, I thought I had to point it anyway on Mailing
> List but then it's useless because you pick patches from Patchwork in
> the end.

Absolutely: if you already mark your patches as Superseded in
patchwork, then there is no need to say anything on the mailing list.
Your patches marked as "Superseded" are no longer part of the
maintainers "TODO-list" on patchwork, so we will only consider your new
version/iteration of the patch.

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:[~2023-08-04 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 14:16 [Buildroot] [PATCH] package/harfbuzz: bump version to 8.1.0 Giulio Benetti
2023-08-04 19:40 ` Giulio Benetti
2023-08-04 20:18   ` Thomas Petazzoni via buildroot
2023-08-04 20:25     ` Giulio Benetti
2023-08-04 20:28       ` 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=20230804222846.0d1b93c7@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.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