From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c954b6acdccddaa7cda03f9cebb7db21e36123d5
Date: Fri, 08 Apr 2016 15:45:44 +0100 [thread overview]
Message-ID: <20160408144544.64E821081BA6@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 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 c954b6acdccddaa7cda03f9cebb7db21e36123d5 (commit)
from 31db25e52bc08e17a789f297bb2f7e2985380075 (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 c954b6acdccddaa7cda03f9cebb7db21e36123d5
Author: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
Date: Thu Apr 7 19:37:06 2016 +0200
bwm-ng: update to 0.6.1
Signed-off-by: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/bwm-ng | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/bwm-ng b/lfs/bwm-ng
index 65f22a3..c989757 100644
--- a/lfs/bwm-ng
+++ b/lfs/bwm-ng
@@ -24,7 +24,7 @@
include Config
-VER = 0.6
+VER = 0.6.1
THISAPP = bwm-ng-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = d3a02484fb7946371bfb4e10927cebfb
+$(DL_FILE)_MD5 = ef0c7669508e95f56250ad4f8db98b7f
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-04-08 14:45 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=20160408144544.64E821081BA6@git01.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