From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 36c9bf685e6be90ff81df19978df1fc34f9cde8f
Date: Wed, 28 Aug 2024 14:59:15 +0000 [thread overview]
Message-ID: <4Wv6xv50y1z2xPM@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 36c9bf685e6be90ff81df19978df1fc34f9cde8f (commit)
from 1c64d2071382093a5d87e875e34850cf071bc292 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 36c9bf685e6be90ff81df19978df1fc34f9cde8f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Aug 27 10:22:03 2024 +0000
make.sh: Bump the toolchain version
This is because of the recent update of binutils.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index a0ea4a99d..8c5e1c6e7 100755
--- a/make.sh
+++ b/make.sh
@@ -32,7 +32,7 @@ GIT_BRANCH="$(git rev-parse --abbrev-ref HEAD)" # Git Branch
GIT_TAG="$(git tag | tail -1)" # Git Tag
GIT_LASTCOMMIT="$(git rev-parse --verify HEAD)" # Last commit
-TOOLCHAINVER=20240802
+TOOLCHAINVER=20240827
KVER_SUFFIX="-${SNAME}"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-08-28 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4Wv6xv50y1z2xPM@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox