From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ab9e4795f1cfb735656ad7b0639af561545e6083
Date: Wed, 14 Jul 2021 18:05:16 +0000 [thread overview]
Message-ID: <4GQ5586fP3z2xjj@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 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 ab9e4795f1cfb735656ad7b0639af561545e6083 (commit)
from f50b0cbf980b89f5673d0a85a49d1d387e94a6ac (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 ab9e4795f1cfb735656ad7b0639af561545e6083
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Jul 14 20:04:02 2021 +0200
cpufrequtils: enable build on all arches
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/cpufrequtils | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/lfs/cpufrequtils b/lfs/cpufrequtils
index ddc03a18b..3c1f5939a 100644
--- a/lfs/cpufrequtils
+++ b/lfs/cpufrequtils
@@ -31,7 +31,6 @@ DL_FILE = $(THISAPP).tar.bz2
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
-SUP_ARCH = x86_64 i586
PROG = cpufrequtils
PAK_VER = 10
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-07-14 18:05 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=4GQ5586fP3z2xjj@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