From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 1350598261d8f5d6b040e0fb9d30cb89f260dadb
Date: Thu, 21 Nov 2013 08:14:54 +0100 [thread overview]
Message-ID: <20131121071456.88E8721542@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1387 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 1350598261d8f5d6b040e0fb9d30cb89f260dadb (commit)
from d30819033d52eea130bde7d118255d9606654bf8 (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 1350598261d8f5d6b040e0fb9d30cb89f260dadb
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Nov 21 08:10:21 2013 +0100
remove old openssh updater rootfile.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/73/filelists/openssh | 1 -
1 file changed, 1 deletion(-)
delete mode 120000 config/rootfiles/core/73/filelists/openssh
Difference in files:
diff --git a/config/rootfiles/core/73/filelists/openssh b/config/rootfiles/core/73/filelists/openssh
deleted file mode 120000
index d8c77fd..0000000
--- a/config/rootfiles/core/73/filelists/openssh
+++ /dev/null
@@ -1 +0,0 @@
-../../../common/openssh
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-11-21 7:14 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=20131121071456.88E8721542@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