From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] header.pl: Add reference to colors.txt into header.pl
Date: Fri, 17 Mar 2023 17:11:57 +0100 [thread overview]
Message-ID: <3dff265c-1010-ab75-9ac5-690670d5ab4b@ipfire.org> (raw)
In-Reply-To: <20230316103403.3761-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Reviewed-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
Tested-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
Am 16.03.2023 um 11:34 schrieb Adolf Belka:
> - With change of common css entries into header.pl with commit
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=b52a84ddc77f9db7e4ad7b129f21fbf528c6f990
> I had missed that color20 and color22 etc, that come from colors.txt, are not known in
> header.pl so that the alternate colours in tables were missing. Even though I tested the
> previous commit I obviously did not look well enough because I missed that the tables
> had no alternate colours. I just found it now when looking at Core Update 174 Testing.
> - Confirmed by copying this version of header.pl into my CU174 Testing system and the
> alternate colour rows came back again as they should be. I am sure now that they are
> correct.
>
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/cfgroot/header.pl | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/config/cfgroot/header.pl b/config/cfgroot/header.pl
> index 955ed2646..3f80ce9b4 100644
> --- a/config/cfgroot/header.pl
> +++ b/config/cfgroot/header.pl
> @@ -17,6 +17,9 @@ use HTML::Entities();
> use Socket;
> use Time::Local;
>
> +our %color = ();
> +&General::readhash("/srv/web/ipfire/html/themes/ipfire/include/colors.txt", \%color);
> +
> $|=1; # line buffering
>
> $Header::revision = 'final';
prev parent reply other threads:[~2023-03-17 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 10:34 Adolf Belka
2023-03-17 16:11 ` Bernhard Bitsch [this message]
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=3dff265c-1010-ab75-9ac5-690670d5ab4b@ipfire.org \
--to=bbitsch@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