public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: [PATCH] dhcp.cgi: Fix for bug #12050
Date: Wed, 05 Jun 2019 15:10:53 +0200	[thread overview]
Message-ID: <trinity-e04319bb-a7cc-4311-8342-1e67b1385b1d-1559740253622@3c-app-gmx-bs55> (raw)
In-Reply-To: <DEA2763F-07F2-4C77-A3AF-67BCC524A2BC@ipfire.org>

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

Hi,

> Gesendet: Mittwoch, 05. Juni 2019 um 14:06 Uhr
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: "Bernhard Bitsch" <Bernhard.Bitsch(a)gmx.de>
> Cc: "IPFire Development" <development(a)lists.ipfire.org>
> Betreff: Re: [PATCH] dhcp.cgi: Fix for bug #12050
>
> Hi,
> 
> > On 5 Jun 2019, at 12:13, Bernhard Bitsch <Bernhard.Bitsch(a)gmx.de> wrote:
> > 
> > Hello,
> > 
> > Thanks for the merge.
> > 
> >> Gesendet: Mittwoch, 05. Juni 2019 um 11:05 Uhr
> >> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> >> An: "Bernhard Bitsch" <Bernhard.Bitsch(a)gmx.de>
> >> Cc: "IPFire Development" <development(a)lists.ipfire.org>
> >> Betreff: Re: [PATCH] dhcp.cgi: Fix for bug #12050
> >> 
> >> Hello,
> >> 
> >> I merged this patch.
> >> 
> >> I had to spend a little time to figure out what you actually wanted to achieve here. It would have helped to add to the commit message that the expected behaviour just wasn’t programmed into the file and that this patch now changes that.
> >> 
> > 
> > The commit message just describes what has changed. The new entry is just added to the file.
> > It is not the "one-click-solution" I would prefer, too.
> > I can submit a patch for this functionality, if we want to do it this way.
> 
> I tested the patch and I could add an extra from the fixed list with one click.
> 
> What are you referring to?
> 

Okay it is a mix-up. For editing the new entry is added to the fixed leases list. Thus if I skip the edit step, the entry is contained anyway, but it is not sorted in.
A one-click-solution should add the new entry, sort the list and return to default state of the page.

> > 
> >> I updated the commit message for your future reference. Please read through that and take some inspiration from that with your next patch.
> >> 
> > I've read your message. If the patch contained this functionality I would have stated that in this way.
> 
> What does the patch do from your point of view?
> 

It only synchronises the internal fixed leases list and the fixed leases file, without synching the sort order. 

> > 
> >> I am happy that we can finally close this bug.
> >> 
> > So am I.
> > 
> > Best,
> > Bernhard
> > 
> >> Best,
> >> -Michael
> >> 
> >>> On 4 Jun 2019, at 11:24, Bernhard Bitsch <Bernhard.Bitsch(a)gmx.de> wrote:
> >>> 
> >>> Save fixed leases to file after addition of a new lease
> >>> 
> >>> Signed-off-by: Bernhard Bitsch <bbitsch(a)ipfire.org>
> >>> 
> >>> ---
> >>> html/cgi-bin/dhcp.cgi | 3 +++
> >>> 1 file changed, 3 insertions(+)
> >>> 
> >>> diff --git a/html/cgi-bin/dhcp.cgi b/html/cgi-bin/dhcp.cgi
> >>> index 675d80012..19c55eb6d 100644
> >>> --- a/html/cgi-bin/dhcp.cgi
> >>> +++ b/html/cgi-bin/dhcp.cgi
> >>> @@ -443,6 +443,9 @@ if ($dhcpsettings{'ACTION'} eq $Lang::tr{'add'}.'2') {
> >>> 	$dhcpsettings{'FIX_ROOTPATH'} = &Header::cleanhtml($dhcpsettings{'FIX_ROOTPATH'});
> >>> 	if ($dhcpsettings{'KEY2'} eq '') { #add or edit ?
> >>> 	    unshift (@current2, "$dhcpsettings{'FIX_MAC'},$dhcpsettings{'FIX_ADDR'},$dhcpsettings{'FIX_ENABLED'},$dhcpsettings{'FIX_NEXTADDR'},$dhcpsettings{'FIX_FILENAME'},$dhcpsettings{'FIX_ROOTPATH'},$dhcpsettings{'FIX_REMARK'}\n");
> >>> +	    open(FILE, ">$filename2") or die 'Unable to open fixed lease file.';
> >>> +	    print FILE @current2;
> >>> +	    close(FILE);
> >>> 	    &General::log($Lang::tr{'fixed ip lease added'});
> >>> 
> >>> 	    # Enter edit mode
> >>> --
> >>> 2.21.0.windows.1
> >>> 
> >> 
> >> 
> 
>

  reply	other threads:[~2019-06-05 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 10:24 Bernhard Bitsch
2019-06-04 12:33 ` Michael Tremer
2019-06-04 12:45   ` Aw: " Bernhard Bitsch
2019-06-05  9:05 ` Michael Tremer
2019-06-05 11:13   ` Aw: " Bernhard Bitsch
2019-06-05 12:06     ` Michael Tremer
2019-06-05 13:10       ` Bernhard Bitsch [this message]
2019-06-05 13:26         ` Michael Tremer
2019-06-05 14:03           ` Aw: " Bernhard Bitsch

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=trinity-e04319bb-a7cc-4311-8342-1e67b1385b1d-1559740253622@3c-app-gmx-bs55 \
    --to=bernhard.bitsch@gmx.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