From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d12e3fcd1e90188b9ddc31dc84334a8e6a5274a8
Date: Mon, 20 May 2019 06:27:24 +0100 [thread overview]
Message-ID: <20190520052725.5D2DC84FDBF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1686 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 d12e3fcd1e90188b9ddc31dc84334a8e6a5274a8 (commit)
from 9961167a52ef80da63f8bc065360119de688f727 (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 d12e3fcd1e90188b9ddc31dc84334a8e6a5274a8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon May 20 07:24:04 2019 +0200
make.sh: comment to update backupiso if version change
It was to offten forgotten to update the backupiso script
that need to download the matching iso from the servers
so i added a comment.
no functional change
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/make.sh b/make.sh
index bfcc83709..ea593370b 100755
--- a/make.sh
+++ b/make.sh
@@ -24,6 +24,7 @@
NAME="IPFire" # Software name
SNAME="ipfire" # Short name
+# If you update the version don't forget to update backupiso and add it to core update
VERSION="2.23" # Version number
CORE="132" # Core Level (Filename)
PAKFIRE_CORE="131" # Core Level (PAKFIRE)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-05-20 5:27 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=20190520052725.5D2DC84FDBF@people01.i.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