From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1a4e9c9db4857d0a578bcd5f4d4a60edc5129834
Date: Thu, 04 Feb 2021 17:58:24 +0000 [thread overview]
Message-ID: <4DWmW460h7z2xSv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 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 1a4e9c9db4857d0a578bcd5f4d4a60edc5129834 (commit)
from 67fbd255d1f9b609bcdf241b3bc6d30eba46f1d5 (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 1a4e9c9db4857d0a578bcd5f4d4a60edc5129834
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Feb 4 17:58:08 2021 +0000
fireperf: Add pakfire packaging meta data
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/fireperf | 2 ++
1 file changed, 2 insertions(+)
Difference in files:
diff --git a/lfs/fireperf b/lfs/fireperf
index c06723c7d..bb88d290e 100644
--- a/lfs/fireperf
+++ b/lfs/fireperf
@@ -31,6 +31,8 @@ DL_FILE = $(THISAPP).tar.gz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
+PROG = fireperf
+PAK_VER = 1
###############################################################################
# Top-level Rules
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-02-04 17:58 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=4DWmW460h7z2xSv@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