From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 03e4f8d60e5671bdc1ec90a829b1f389bcd0b8aa
Date: Thu, 16 Apr 2020 05:43:07 +0000 [thread overview]
Message-ID: <492p6M6YdLz2y5N@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1662 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 03e4f8d60e5671bdc1ec90a829b1f389bcd0b8aa (commit)
from 296675c9ee3b984b5bfb5bdff032cdd2375639a3 (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 03e4f8d60e5671bdc1ec90a829b1f389bcd0b8aa
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Wed Apr 15 18:19:03 2020 +0200
dhcpcd: Update to 9.0.1
For details see:
https://roy.marples.name/archives/dhcpcd-discuss/0002921.html
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/dhcpcd | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/dhcpcd b/lfs/dhcpcd
index c9aa45b50..0216ae2fd 100644
--- a/lfs/dhcpcd
+++ b/lfs/dhcpcd
@@ -24,7 +24,7 @@
include Config
-VER = 9.0.0
+VER = 9.0.1
THISAPP = dhcpcd-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 5360da47d4d51280dae35fe91958b63a
+$(DL_FILE)_MD5 = e893186a0c64adce6da47c33f4984951
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-04-16 5:43 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=492p6M6YdLz2y5N@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