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, fifteen, updated. 5ae3072a47b8c2296d3b6bd25516284bf97b3cdc
Date: Fri, 04 Oct 2013 08:38:57 +0200	[thread overview]
Message-ID: <20131004063857.96E0320F76@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1406 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, fifteen has been updated
       via  5ae3072a47b8c2296d3b6bd25516284bf97b3cdc (commit)
      from  b3cc5fbdb9f800b809c3bcd2f1d72fdd5c2b7e62 (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 5ae3072a47b8c2296d3b6bd25516284bf97b3cdc
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Oct 4 08:37:49 2013 +0200

    remove php from core73.
    
    fifteen branch will not build with this file.

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

Summary of changes:
 config/rootfiles/core/73/filelists/php | 1 -
 1 file changed, 1 deletion(-)
 delete mode 120000 config/rootfiles/core/73/filelists/php

Difference in files:
diff --git a/config/rootfiles/core/73/filelists/php b/config/rootfiles/core/73/filelists/php
deleted file mode 120000
index 1ae48d7..0000000
--- a/config/rootfiles/core/73/filelists/php
+++ /dev/null
@@ -1 +0,0 @@
-../../../common/php
\ No newline at end of file


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

                 reply	other threads:[~2013-10-04  6:38 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=20131004063857.96E0320F76@argus.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