From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Buildroot Development <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/2] package/git: bump to version 2.40.0
Date: Tue, 14 Mar 2023 23:27:08 +0100 [thread overview]
Message-ID: <20230314232708.674f4e3a@windsurf> (raw)
In-Reply-To: <20230314095234.284584-2-bagasdotme@gmail.com>
On Tue, 14 Mar 2023 16:52:33 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> Bump the package to v2.40.0. The release announcement and
> notes are at [1].
>
> While at it, also drop two Buildroot patches as these have been
> already applied upstream.
>
> [1]: https://lore.kernel.org/git/xmqqjzzkv8xz.fsf@gitster.g/
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> ...avoid-redefining-system-function-nam.patch | 109 ------------------
> ...undefine-system-names-before-redecla.patch | 55 ---------
> package/git/git.hash | 2 +-
> package/git/git.mk | 2 +-
> 4 files changed, 2 insertions(+), 166 deletions(-)
> delete mode 100644 package/git/0001-git-compat-util-avoid-redefining-system-function-nam.patch
> delete mode 100644 package/git/0002-git-compat-util-undefine-system-names-before-redecla.patch
Both patches of this series 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
next prev parent reply other threads:[~2023-03-14 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 9:52 [Buildroot] [PATCH 0/2] git version bump Bagas Sanjaya
2023-03-14 9:52 ` [Buildroot] [PATCH 1/2] package/git: bump to version 2.40.0 Bagas Sanjaya
2023-03-14 22:27 ` Thomas Petazzoni via buildroot [this message]
2023-03-14 9:52 ` [Buildroot] [PATCH 2/2] DEVELOPERS: Add entry for Bagas Sanjaya as Buildroot developer for git Bagas Sanjaya
2023-03-19 16:48 ` Peter Korsgaard
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=20230314232708.674f4e3a@windsurf \
--to=buildroot@buildroot.org \
--cc=bagasdotme@gmail.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 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.