All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org,
	Marcus Folkesson <marcus.folkesson@gmail.com>,
	Kamel Bouhara <kamel.bouhara@gmail.com>,
	Woodrow Douglass <wdouglass@carnegierobotics.com>,
	Julien Olivain <ju.o@free.fr>, Asaf Kahlon <asafka7@gmail.com>,
	Marcin Niestroj <m.niestroj@grinn-global.com>,
	Christian Stewart <christian@aperture.us>,
	Robert Rose <robertroyrose@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: Re: [Buildroot] [PATCH v4 3/6] package/pkgconf: bump to version 2.3.0
Date: Wed, 6 Nov 2024 22:21:51 +0100	[thread overview]
Message-ID: <20241106222151.2ecd0926@windsurf> (raw)
In-Reply-To: <20241030190020.1444105-3-james.hilliard1@gmail.com>

On Wed, 30 Oct 2024 13:00:17 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> Rebase only prefix subset of variables patch.
> 
> Drop revert main assume modversion patch which is now upstream.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  .checkpackageignore                           |  1 -
>  ...th-the-sysroot-a-subset-of-variables.patch | 78 ++++++++++---------
>  ...me-modversion-insted-of-version-if-o.patch | 45 -----------
>  package/pkgconf/pkgconf.hash                  |  2 +-
>  package/pkgconf/pkgconf.mk                    |  2 +-
>  5 files changed, 42 insertions(+), 86 deletions(-)
>  delete mode 100644 package/pkgconf/0002-Revert-main-assume-modversion-insted-of-version-if-o.patch

Applied to next, 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-11-06 21:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 19:00 [Buildroot] [PATCH v4 1/6] package/{python-}protobuf: bump to version 28.1 James Hilliard
2024-10-30 19:00 ` [Buildroot] [PATCH v4 2/6] package/grpc: bump to version 1.66.1 James Hilliard
2024-11-06 21:30   ` Thomas Petazzoni via buildroot
2024-10-30 19:00 ` [Buildroot] [PATCH v4 3/6] package/pkgconf: bump to version 2.3.0 James Hilliard
2024-11-06 21:21   ` Thomas Petazzoni via buildroot [this message]
2024-10-30 19:00 ` [Buildroot] [PATCH v4 4/6] package/protobuf-c: fix protobuf >= 26.0 compatibility James Hilliard
2024-11-06 21:22   ` Thomas Petazzoni via buildroot
2024-10-30 19:00 ` [Buildroot] [PATCH v4 5/6] package/mosh: fix compatibility with newer protobuf versions James Hilliard
2024-11-06 21:21   ` Thomas Petazzoni via buildroot
2024-10-30 19:00 ` [Buildroot] [PATCH v4 6/6] package/collectd: fix protoc version check James Hilliard
2024-11-06 21:21   ` Thomas Petazzoni via buildroot
2024-11-06 21:26 ` [Buildroot] [PATCH v4 1/6] package/{python-}protobuf: bump to version 28.1 Thomas Petazzoni 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=20241106222151.2ecd0926@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=christian@aperture.us \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=kamel.bouhara@gmail.com \
    --cc=m.niestroj@grinn-global.com \
    --cc=marcus.folkesson@gmail.com \
    --cc=robertroyrose@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wdouglass@carnegierobotics.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.