From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8318a967e2d1ff2882cd2c670dc0f5ead256e844
Date: Thu, 19 Jan 2023 11:01:01 +0000 [thread overview]
Message-ID: <4NyKRx5563z2xg7@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 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 8318a967e2d1ff2882cd2c670dc0f5ead256e844 (commit)
from 42341a74039e04cd134f8f262fcecba1741de773 (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 8318a967e2d1ff2882cd2c670dc0f5ead256e844
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Thu Jan 19 11:00:23 2023 +0000
make.sh: Remove dropped spandsp add-on
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 6488a7738..5ce67b64b 100755
--- a/make.sh
+++ b/make.sh
@@ -1454,7 +1454,6 @@ buildipfire() {
lfsmake2 vlan
lfsmake2 wireless
lfsmake2 pakfire
- lfsmake2 spandsp
lfsmake2 lz4
lfsmake2 lzo
lfsmake2 openvpn
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-01-19 11:01 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=4NyKRx5563z2xg7@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