public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 120cedf2852b71cd06cdacda10a18a8e7f2eeb8a
Date: Sat, 21 Jan 2012 17:17:55 +0100	[thread overview]
Message-ID: <20120121161759.22F8F20DA2@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2298 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  120cedf2852b71cd06cdacda10a18a8e7f2eeb8a (commit)
      from  18252bf79499ec809dc4f4eeba6fecffd50bd3e6 (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 120cedf2852b71cd06cdacda10a18a8e7f2eeb8a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Jan 21 17:17:35 2012 +0100

    python-m2crypto: rootfile update.

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

Summary of changes:
 config/rootfiles/common/armv5tel/python-m2crypto |    1 +
 config/rootfiles/common/i586/python-m2crypto     |    1 +
 config/rootfiles/common/python-m2crypto          |    1 -
 3 files changed, 2 insertions(+), 1 deletions(-)
 create mode 100644 config/rootfiles/common/armv5tel/python-m2crypto
 create mode 100644 config/rootfiles/common/i586/python-m2crypto
 delete mode 100644 config/rootfiles/common/python-m2crypto

Difference in files:
diff --git a/config/rootfiles/common/armv5tel/python-m2crypto b/config/rootfiles/common/armv5tel/python-m2crypto
new file mode 100644
index 0000000..6f51e3d
--- /dev/null
+++ b/config/rootfiles/common/armv5tel/python-m2crypto
@@ -0,0 +1 @@
+#usr/lib/python2.7/site-packages/M2Crypto-0.21.1-py2.7-linux-armv5tel.egg
diff --git a/config/rootfiles/common/i586/python-m2crypto b/config/rootfiles/common/i586/python-m2crypto
new file mode 100644
index 0000000..7317214
--- /dev/null
+++ b/config/rootfiles/common/i586/python-m2crypto
@@ -0,0 +1 @@
+#usr/lib/python2.7/site-packages/M2Crypto-0.21.1-py2.7-linux-i586.egg
diff --git a/config/rootfiles/common/python-m2crypto b/config/rootfiles/common/python-m2crypto
deleted file mode 100644
index 1f20672..0000000
--- a/config/rootfiles/common/python-m2crypto
+++ /dev/null
@@ -1 +0,0 @@
-#usr/lib/python2.7/site-packages/M2Crypto-0.21.1-py2.7-linux-i686.egg


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

                 reply	other threads:[~2012-01-21 16: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=20120121161759.22F8F20DA2@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