public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 'resolv' => 'Resolv-Retry', = Obsolete?
Date: Mon, 06 Feb 2017 19:29:39 +0100	[thread overview]
Message-ID: <07ed3c96-66b3-77ba-4f2b-3330959450f0@ipfire.org> (raw)
In-Reply-To: <D72ACE2D-1ACE-4FE9-93E8-88B2EEAA0801@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

On 06.02.2017 16:26, ummeegge wrote:
> Hi Matthias,

Hi Erik,

> the first and important one, i made some more stuff on that script (forgot to delete the unused polish strings) and have added also a check after deletion if strings could not be deleted. Now it takes a only little longer :-)=) but it might be also a little more user-friendly…

Besides, you're acting in the future already: "$date: 03.05.2017"!? ;-))

> Updated script can be found in here --> https://raw.githubusercontent.com/ummeegge/scripts/master/langsCleaner.sh .

Thanks! - downloaded. As soon as I "have my hands free", I'll test this.
A week of work has started, and "she seems to be kind of bad-tempered"...

Some thoughts:
I saw, your script uses "grep -FR" to build the string lists, so that
the *.dat-files in '/srv/web/ipfire/cgi-bin/logs.cgi' are included in
the search!?

What about the strings in '/var/ipfire/addon-lang/*.pl'?

Best,
Matthias

  reply	other threads:[~2017-02-06 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bd4c095b-9fea-9f36-9f78-d9246eacbb21@ipfire.org>
2017-02-06 15:26 ` ummeegge
2017-02-06 18:29   ` Matthias Fischer [this message]
     [not found] <0436f51f-7ffc-cccf-d3c5-87c66b4c4741@ipfire.org>
2017-02-07  9:52 ` ummeegge
2017-02-07 18:19   ` Matthias Fischer
2017-02-08  4:18     ` ummeegge
2017-02-04 16:19 Matthias Fischer
2017-02-04 16:32 ` IT Superhack
2017-02-04 17:34   ` Matthias Fischer

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=07ed3c96-66b3-77ba-4f2b-3330959450f0@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --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