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, next, updated. 4f4f5bbbfded965d41429d438efba429794aae8a
Date: Tue, 15 Aug 2017 12:11:18 +0100	[thread overview]
Message-ID: <20170815111118.6550C1081DE1@git01.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1385 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  4f4f5bbbfded965d41429d438efba429794aae8a (commit)
      from  5564841b1055082190e544d0a2e3c611139648f4 (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 4f4f5bbbfded965d41429d438efba429794aae8a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Aug 15 12:02:12 2017 +0100

    logrotate: Fix source tarball checksum
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

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

Difference in files:
diff --git a/lfs/logrotate b/lfs/logrotate
index b047327..70e9f48 100644
--- a/lfs/logrotate
+++ b/lfs/logrotate
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = d1c41bdf63b9993c8e4e8b48a7bd5b8b
+$(DL_FILE)_MD5 = 3162ada6f1036c1a4a0a68262989ff73
 
 install : $(TARGET)
 


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

                 reply	other threads:[~2017-08-15 11:11 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=20170815111118.6550C1081DE1@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