All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@busybox.net
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH] package/fmt: bump to version 12.2.0
Date: Sun, 05 Jul 2026 19:33:14 +0200	[thread overview]
Message-ID: <pan$27394$5a9561a$c8874897$7817ee3f@ID-313208.user.individual.net> (raw)
In-Reply-To: b5dd30852bde29c27b79e9d92f3a1c29@free.fr

Hi Julien,

Am Sun, 05 Jul 2026 18:48:01 +0200 schrieb Julien Olivain via buildroot:

> For some reason, your message was not displayed in patchwork:
> https://patchwork.ozlabs.org/project/buildroot/patch/
20260629071429.4131207-2-buildroot@heine.tech/

I guess because the patchwork URLs contain mail addresses which are 
anonymized when posting through news.gmane.io:

References: <20260629071429.4131207-2-
buildroot__14354.4681415491$1782717305$gmane$org@heine.tech>

according to https://lists.buildroot.org/pipermail/buildroot/2026-
June.txt.gz

> So I missed it and applied the fmt bump. I guess we'll need the patches
> for fixing the gerbera package.

Done: https://patchwork.ozlabs.org/project/buildroot/patch/
20260705172616.3104270-1-bernd@kuhls.net/

Regards, Bernd

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-07-05 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260629071429.4131207-2-buildroot__14354.4681415491$1782717305$gmane$org@heine.tech>
2026-06-29 13:02 ` [Buildroot] [PATCH] package/fmt: bump to version 12.2.0 Bernd Kuhls
2026-07-05 16:48   ` Julien Olivain via buildroot
2026-07-05 17:33     ` Bernd Kuhls [this message]
2026-06-29  7:14 Michael Nosthoff via buildroot
2026-07-05 16:46 ` Julien Olivain 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='pan$27394$5a9561a$c8874897$7817ee3f@ID-313208.user.individual.net' \
    --to=bernd@kuhls.net \
    --cc=buildroot@busybox.net \
    --cc=buildroot@uclibc.org \
    /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.