From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: [PATCH] dhcpcd: Update to 9.1.3
Date: Sat, 04 Jul 2020 12:23:50 +0200 [thread overview]
Message-ID: <trinity-3cb30558-0aef-4d82-b4a8-56f46be25219-1593858230412@3c-app-gmx-bap33> (raw)
In-Reply-To: <181D6533-77ED-459D-8AE6-069B2DBDD4A7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
Hi,
looking at the traffic in the mailing list of dhcpcd, I think this is a (hopefully) temporary phenomenon. As far I can see, Roy Marples made some deep changes to the code, for restructuring, ... Those changes always make in noise in the development and testing process.
Do we have a possibility, to participate in the testing process of dhcpcd? We have a somewhat broad user community, but the DHCP client is a essential part for all installations using a DHCP WAN connection.
Currently I see issues with the client, when the ISP changes my IP. Because this happens in the night ( 1.00 am to 2.30 am ), I haven't examined this in depth, yet.
-Bernhard
> Gesendet: Samstag, 04. Juli 2020 um 11:32 Uhr
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: "Matthias Fischer" <matthias.fischer(a)ipfire.org>
> Cc: development(a)lists.ipfire.org
> Betreff: Re: [PATCH] dhcpcd: Update to 9.1.3
>
> Hi,
>
> So since there is a lot of releases, can we come up with some sort of regular update cycle?
>
> I do not think it makes sense to build every single release, because there will always be another one. Should we limit ourselves to about one a month or something like that?
>
> -Michael
>
> > On 3 Jul 2020, at 17:09, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> >
> > Hi,
> >
> > On 03.07.2020 11:37, Michael Tremer wrote:
> >> Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> >>
> >> Very interesting how much you can develop around a simple DHCP client :)
> >>
> > ...
> > And guess what? 9.3.4 is out.
> >
> > Please don't merge...the next patch is on his way. *sigh*
> >
> > Best,
> > Matthias
>
>
next prev parent reply other threads:[~2020-07-04 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 20:43 Matthias Fischer
2020-07-03 9:37 ` Michael Tremer
2020-07-03 16:09 ` Matthias Fischer
2020-07-04 9:32 ` Michael Tremer
2020-07-04 10:23 ` Bernhard Bitsch [this message]
2020-07-05 8:44 ` Aw: " Matthias Fischer
2020-07-05 8:44 ` 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=trinity-3cb30558-0aef-4d82-b4a8-56f46be25219-1593858230412@3c-app-gmx-bap33 \
--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