From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9856eec1cc29874d162fa67c9e9e1173d120aba2
Date: Fri, 26 Apr 2013 12:02:45 +0200 [thread overview]
Message-ID: <20130426100246.2C2DB200BD@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1470 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 9856eec1cc29874d162fa67c9e9e1173d120aba2 (commit)
from 158a431825715cbee07a12a78bea7f2430c4b58d (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 9856eec1cc29874d162fa67c9e9e1173d120aba2
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Apr 26 12:02:26 2013 +0200
Add perl-Sort-Natually module to core update 68.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/68/filelists/perl-Sort-Naturally | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/68/filelists/perl-Sort-Naturally
Difference in files:
diff --git a/config/rootfiles/core/68/filelists/perl-Sort-Naturally b/config/rootfiles/core/68/filelists/perl-Sort-Naturally
new file mode 120000
index 0000000..9d70650
--- /dev/null
+++ b/config/rootfiles/core/68/filelists/perl-Sort-Naturally
@@ -0,0 +1 @@
+../../../common/perl-Sort-Naturally
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-04-26 10:02 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=20130426100246.2C2DB200BD@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