public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. f7eab091642b641df1c2e49b63d0fc065afefda4
Date: Thu, 08 Jun 2017 13:24:28 +0100	[thread overview]
Message-ID: <20170608122437.64CEB1078E83@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1625 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, master has been updated
       via  f7eab091642b641df1c2e49b63d0fc065afefda4 (commit)
      from  3b1c776259eba53514c6fa4c120d919b7f3f365e (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 f7eab091642b641df1c2e49b63d0fc065afefda4
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Thu Jun 8 14:15:49 2017 +0200

    guardian: Bump package version
    
    During commit d68ead3decfdcc4ca4a1413e33f3c47270799836 the guardian.cgi
    has been changed, and therefore the package version of guardian
    needs to be bumped to ship the changed files.
    
    Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/guardian | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/guardian b/lfs/guardian
index 2120a08..f3001c8 100644
--- a/lfs/guardian
+++ b/lfs/guardian
@@ -33,7 +33,7 @@ DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 
 PROG       = guardian
-PAK_VER    = 13
+PAK_VER    = 14
 
 DEPS       = "perl-inotify2 perl-Net-IP"
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2017-06-08 12:24 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=20170608122437.64CEB1078E83@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