Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad.86@gmail.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] DEVELOPERS: update email for Francois Perrad
Date: Fri, 31 Jul 2026 14:05:08 +0200	[thread overview]
Message-ID: <20260731120508.3342-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260720184652.252941-1-francois.perrad.86@gmail.com>

In reply of:
> Signed-off-by: Francois Perrad <francois.perrad.86@gmail.com>

Applied to 2025.02.x & 2026.05.x. Thanks

> ---
>  DEVELOPERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/DEVELOPERS b/DEVELOPERS
> index c5d6dbd8b..934209d7d 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -1162,7 +1162,7 @@ F:	board/visionfive2/
>  F:	configs/sipeed_licheepi_nano_defconfig
>  F:	configs/visionfive2_defconfig
>  
> -N:	Francois Perrad <francois.perrad@gadz.org>
> +N:	Francois Perrad <francois.perrad.86@gmail.com>
>  F:	board/olimex/a20_olinuxino
>  F:	board/olimex/imx233_olinuxino/
>  F:	board/olimex/stmp1_olinuxino/
> -- 
> 2.43.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-07-31 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 18:46 [Buildroot] [PATCH] DEVELOPERS: update email for Francois Perrad Francois Perrad
2026-07-20 19:24 ` Julien Olivain via buildroot
2026-07-31 12:05 ` Thomas Perale via buildroot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-20 18:43 Francois Perrad

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=20260731120508.3342-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=francois.perrad.86@gmail.com \
    --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