public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core181, updated. 84f8640da0f2550a9b2a35299a0dd5d7059c4d19
Date: Tue, 28 Nov 2023 16:18:59 +0000	[thread overview]
Message-ID: <4SfnhM6rS2z2xft@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1496 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, core181 has been updated
       via  84f8640da0f2550a9b2a35299a0dd5d7059c4d19 (commit)
      from  ece94c7edfa45b724ef05b57ff7a8a18c43fb99b (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 84f8640da0f2550a9b2a35299a0dd5d7059c4d19
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Nov 28 16:18:39 2023 +0000

    core181: Ship apache initscript
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 config/rootfiles/core/181/filelists/files | 1 +
 1 file changed, 1 insertion(+)

Difference in files:
diff --git a/config/rootfiles/core/181/filelists/files b/config/rootfiles/core/181/filelists/files
index 4bed8098d..09ab7430e 100644
--- a/config/rootfiles/core/181/filelists/files
+++ b/config/rootfiles/core/181/filelists/files
@@ -1,3 +1,4 @@
+etc/rc.d/init.d/apache
 srv/web/ipfire/cgi-bin/extrahd.cgi
 srv/web/ipfire/cgi-bin/ovpnmain.cgi
 srv/web/ipfire/cgi-bin/urlfilter.cgi


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

                 reply	other threads:[~2023-11-28 16:18 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=4SfnhM6rS2z2xft@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