From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ad4ce45ae29bfa931ba5fb88bc99dccaccc48303
Date: Thu, 13 Jun 2013 15:05:29 +0200 [thread overview]
Message-ID: <20130613130529.E7356208BB@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 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 ad4ce45ae29bfa931ba5fb88bc99dccaccc48303 (commit)
from a606377ea89d5aa4d8e01022778dae5ad929d800 (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 ad4ce45ae29bfa931ba5fb88bc99dccaccc48303
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Jun 13 15:05:12 2013 +0200
Add libjpeg to core update 70.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/70/filelists/libjpeg | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/70/filelists/libjpeg
Difference in files:
diff --git a/config/rootfiles/core/70/filelists/libjpeg b/config/rootfiles/core/70/filelists/libjpeg
new file mode 120000
index 0000000..3b1a782
--- /dev/null
+++ b/config/rootfiles/core/70/filelists/libjpeg
@@ -0,0 +1 @@
+../../../common/libjpeg
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-06-13 13:05 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=20130613130529.E7356208BB@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