From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8801fc5f95672cf828d15f700c88454a97d1ca9e
Date: Thu, 18 Jun 2015 21:17:39 +0200 [thread overview]
Message-ID: <20150618191739.8BCE8221CE@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1471 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 8801fc5f95672cf828d15f700c88454a97d1ca9e (commit)
from bbdc2e4bcf64a96d3ddd3ae42cbe49341c1a4f59 (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 8801fc5f95672cf828d15f700c88454a97d1ca9e
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jun 18 21:17:14 2015 +0200
core92: The Python update belongs into Core Update 92
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/91/filelists/python | 1 -
1 file changed, 1 deletion(-)
delete mode 120000 config/rootfiles/core/91/filelists/python
Difference in files:
diff --git a/config/rootfiles/core/91/filelists/python b/config/rootfiles/core/91/filelists/python
deleted file mode 120000
index ffe6e2c..0000000
--- a/config/rootfiles/core/91/filelists/python
+++ /dev/null
@@ -1 +0,0 @@
-../../../common/python
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-06-18 19:17 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=20150618191739.8BCE8221CE@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