From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Aw: Re: Patch for bugzilla #12050, try #2
Date: Tue, 16 Apr 2019 18:24:30 +0200 [thread overview]
Message-ID: <743b48c2-8d2b-bdd3-f3f0-ab02604da14a@ipfire.org> (raw)
In-Reply-To: <trinity-38b5454a-5d1d-49f9-9cff-2391fb7318b2-1555354181990@3c-app-gmx-bs79>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
Hi,
@Bernhard:
Right now I've got a Core 130 branch up and running - I could do this
patch for you... Would it be ok if i do?
Best,
Matthias
On 15.04.2019 20:49, Bernhard Bitsch wrote:
> Hi Michael,
>
> I know the "normal way" to send patches.
> But I do not have a up-to-date git repo at the moment, reasons exist but aren't of interest for this special case.
> I have posted the entire modified dhcpi.cgi in the forum for usage. Wanted just to supply the DevList and Bugzilla with a short and fast solution, hoping not to be to late for the announced emergency update.
>
> If you want, I can post the entire modified dhcp.cgi to the DevList and someone of the devs can merge it to the git repository.
>
> - Bernhard
>
> BTW: I'll setup my local repo again. Further patches for this and other problems and/or developments will obey the guidance from wiki.
>
>> Gesendet: Montag, 15. April 2019 um 13:12 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 for bugzilla #12050, try #2
>>
>> Hi Bernhard,
>>
>> I am happy that you are taking a look at this bug, but this is not how the process works.
>>
>> We have a guide on how to submit patches to the mailing list:
>>
>> https://wiki.ipfire.org/devel/submit-patches
>>
>> There are a thousand reasons why we are doing this as we are doing it. Please follow it.
>>
>> -Michael
>>
>> > On 14 Apr 2019, at 00:04, Bernhard Bitsch <Bernhard.Bitsch(a)gmx.de> wrote:
>> >
>> > Please find appended the solution.
>> >
>> > Short description of the problem:
>> >
>> > After adding a new lease, you are in editing mode.
>> > All fields are set right, but a second click ('update' ) is necessary.
>> > With determining the exact mode 'add/edit' this second click can be avoided for new entries ( new MAC/IP combination).
>> >
>> > The patch adds determination of add/edit mode. If the MAC/IP pair exists in the list of fixed leases edit mode is selected, add mode is selected else.
>> >
>> > Sorry, did not produce the patch from git but by diffing changed file and the core 129 original.
>> >
>> > -Bernhard
>> >
>> > EDIT: produced an error by blind copy & paste, should correct with this patch.<dhcp.cgi.patch>
>>
>>
>
next prev parent reply other threads:[~2019-04-16 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 23:04 Bernhard Bitsch
2019-04-15 11:12 ` Michael Tremer
2019-04-15 18:49 ` Aw: " Bernhard Bitsch
2019-04-16 16:24 ` Matthias Fischer [this message]
2019-04-16 16:40 ` 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=743b48c2-8d2b-bdd3-f3f0-ab02604da14a@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