From: Alexander Marx <alexander.marx@oab.de>
To: development@lists.ipfire.org
Subject: Re: CCD Final
Date: Fri, 16 Nov 2012 20:00:57 +0100 [thread overview]
Message-ID: <50A68D69.5020709@oab.de> (raw)
In-Reply-To: <1353083681.1735.82.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2144 bytes --]
Am 16.11.2012 17:34, schrieb Michael Tremer:
> Hello guys,
>
> I merged the changes to the next branch.
>
> http://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=8c877a82f6a63e07e2dde8d55c6e0db4893bf73d
>
> Please note, that this does not mean that testing is done. It has just
> been started.
>
> I also changed a lot of the translation strings. Fixed typos, rephrased
> sentences. Please double check this.
Thanks for that, looks better.
> Stevee will take care of the migration script. Please rename "lang.sh"
> to "update-lang-cache" and put it in /usr/sbin (lfs/stage2).
Sorry, but i checket out next branch and lfs/stage2 is a script? How can
i put the lang.sh (update-lang-cache) into it?
> Michael
>
> On Fri, 2012-11-16 at 06:19 +0100, Alexander Marx wrote:
>> Dear List!
>>
>> Here you get the final release with latest modifications.
>> Git Version is updated.
>>
>> Stevee, one thing for you:
>>
>> We need to run an update script with the core update. The script is in
>> attachment, tools->ccd.pl
>> i don't know where to put it in the git branch, so please make it run
>> once on update.
>>
>> This script looks for existing VPN Clients and builds ccd files with
>> default route to green network.
>> This is needed, because the default route to green is no longer in the
>> server.conf.
>> I modified the script so that there's no Console output.
>> The script needs to stop and start the OVPN server!
>>
>> The lang.sh file should go to /usr/bin/ or /usr/local/bin/ in the next
>> release if possible. It makes it easier to generate the languages,
>> because one only needs to execute "lang.sh"
>>
>> Here i also don't know where to put it in the git.
>>
>>
>>
>> Thank you a lot for reviewing the code and testing.
>>
>> Alex
>> _______________________________________________
>> Development mailing list
>> Development(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2012-11-16 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 5:19 Alexander Marx
2012-11-16 16:34 ` Michael Tremer
2012-11-16 19:00 ` Alexander Marx [this message]
2012-11-19 20:47 ` Stefan Schantl
2012-11-20 3:24 ` Alexander Marx
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=50A68D69.5020709@oab.de \
--to=alexander.marx@oab.de \
--cc=development@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