All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH 2/2] docs/manual: allow sponsor mention in author name
Date: Mon, 8 Jul 2024 23:10:37 +0200	[thread overview]
Message-ID: <20240708231037.5211d7e0@windsurf> (raw)
In-Reply-To: <20240705094449.8550-3-fiona.klute@gmx.de>

On Fri,  5 Jul 2024 11:44:49 +0200
Fiona Klute via buildroot <buildroot@buildroot.org> wrote:

> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
> 
> Unfortunately not all mail providers deliver mails with subaddressing,
> mention people can acknowledge a sponsor in the author name instead.
> 
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>
> ---
>  docs/manual/contribute.adoc | 4 ++++
>  1 file changed, 4 insertions(+)

Applied to master, thanks.

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

      reply	other threads:[~2024-07-08 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05  9:44 [Buildroot] [PATCH 0/2] Manual updates Fiona Klute via buildroot
2024-07-05  9:44 ` [Buildroot] [PATCH 1/2] docs/manual: describe relying on default options Fiona Klute via buildroot
2024-07-08 21:11   ` Thomas Petazzoni via buildroot
2024-07-09  8:38     ` Fiona Klute via buildroot
2024-07-09  9:37       ` Thomas Petazzoni via buildroot
2024-07-09 10:13         ` Arnout Vandecappelle via buildroot
2024-07-09 11:57           ` Thomas Petazzoni via buildroot
2024-07-12  9:49             ` Fiona Klute via buildroot
2024-07-05  9:44 ` [Buildroot] [PATCH 2/2] docs/manual: allow sponsor mention in author name Fiona Klute via buildroot
2024-07-08 21:10   ` 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=20240708231037.5211d7e0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --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.