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. e247eb7cec0c628fb1d0a07e9cec3ced925b53d9
Date: Mon, 23 Jan 2012 22:32:27 +0100	[thread overview]
Message-ID: <20120123213228.1E4FC20145@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2158 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  e247eb7cec0c628fb1d0a07e9cec3ced925b53d9 (commit)
      from  76b8277500d32f633dd9d044d4593aa8a4d17013 (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 e247eb7cec0c628fb1d0a07e9cec3ced925b53d9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Jan 23 22:09:31 2012 +0100

    Allow : character in configuration files.
    
    According to bug #10006, it is needed in some DSL credentials.
    
    As : is not a special character in shell code (at least if
    {} is not allowed either) we can safely use it.

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

Summary of changes:
 config/rootfiles/core/56/filelists/files |    1 +
 src/scripts/readhash                     |    2 +-
 2 files changed, 2 insertions(+), 1 deletions(-)

Difference in files:
diff --git a/config/rootfiles/core/56/filelists/files b/config/rootfiles/core/56/filelists/files
index 58c1960..7b1d4c0 100644
--- a/config/rootfiles/core/56/filelists/files
+++ b/config/rootfiles/core/56/filelists/files
@@ -8,3 +8,4 @@ srv/web/ipfire/cgi-bin/media.cgi
 usr/local/bin/hddshutdown
 usr/local/bin/makegraphs
 usr/local/bin/openvpnctrl
+usr/local/bin/readhash
diff --git a/src/scripts/readhash b/src/scripts/readhash
index 63a3e0f..8c187d5 100644
--- a/src/scripts/readhash
+++ b/src/scripts/readhash
@@ -13,7 +13,7 @@ VARNAME='[A-Za-z_][A-zA-z0-9_]*'
 
 # For the assigned value we only accept a limited number of characters - none
 # of which are shell metachars
-VARCHARS='A-Za-z0-9=/,._@#+-'
+VARCHARS='A-Za-z0-9=/,.:_@#+-'
 VARVAL="[${VARCHARS}]*"
 
 sed -ne "s/\(${VARNAME}\)=\(${VARVAL}\)$/\1=\2/p" $1


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

                 reply	other threads:[~2012-01-23 21:32 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=20120123213228.1E4FC20145@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