public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 174 is available for testing
Date: Thu, 16 Mar 2023 11:42:01 +0100	[thread overview]
Message-ID: <c914dd72-8e5d-f8ff-e928-3f06d94c5855@ipfire.org> (raw)
In-Reply-To: <167894820894.818965.4146077518153143991.ipfire@ipfire.org>

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

Hi Peter,

When I did my change to having the common css variables in header.pl I had missed that colors.txt is not referenced in header.pl so in the dhcp.cgi and updatexlrator.cgi pages the tables show up without the alternate colour bands. I did test my original patches abut obviously my brain ignored my eyes and did not see they were missing.

I found the problem when I upgraded to CU174 Testing.

I have submitted a patch to fix my error.

Regards,
Adolf.

On 16/03/2023 07:30, IPFire Project wrote:
> IPFire Logo
> 
> there is a new post from Michael Tremer on the IPFire Blog:
> 
> *IPFire 2.27 - Core Update 174 is available for testing*
> 
>     The next Core Update is ready for testing: IPFire 2.27 - Core Update 174. It is a traditional spring clean release which updates major parts of the core system and comes with a large number of bug fixes throughout.
> 
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-174-is-available-for-testing>
> 
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

           reply	other threads:[~2023-03-16 10:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <167894820894.818965.4146077518153143991.ipfire@ipfire.org>]

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=c914dd72-8e5d-f8ff-e928-3f06d94c5855@ipfire.org \
    --to=adolf.belka@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