From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dhcpcd: Update to 9.1.3
Date: Sun, 05 Jul 2020 10:44:37 +0200 [thread overview]
Message-ID: <79d54d8a-bd99-6738-322e-d4f37cbbe5f8@ipfire.org> (raw)
In-Reply-To: <181D6533-77ED-459D-8AE6-069B2DBDD4A7@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]
Hi,
On 04.07.2020 11:32, Michael Tremer wrote:
> Hi,
>
> So since there is a lot of releases, can we come up with some sort of regular update cycle?
I'd like to. Otherwise, its often hard to decide whether an update is
*really* important or just "nice to have". Software is evil... ;-)
This is one reason why I stopped pushing every available 'squid 4.12' patch.
E.g., how many IPFire user are affected by "squid-Bug 503" (Negative
caching caches errors from If-Modified-Since requests indefinitely) and
is this a serious bug? For IPFire? Hm. Hard to tell. The same applies to
'dhcpcd'. Which release is important for us?
> I do not think it makes sense to build every single release, because there will always be another one.
Yep. Especially for 'dhcpcd' there were over a dozen releases in the
last half year. But who - and how to - decide(s) what "makes sense"!?
Besides - apart from a few exceptions - I test almost every single patch
before I upload it (yesterday's updates - libvirt, libusbredir, qemu-
are for example such exceptions). And I often sent patches for errors
that I could not reproduce in my environment. Only to prevent them from
appearing with other users.
> Should we limit ourselves to about one a month or something like that?
This would be no problem for me. And it would save some traffic/noise on
the list. As I wrote above: hard to tell...
Best,
Matthias
>
> -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
>
prev parent reply other threads:[~2020-07-05 8:44 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 ` Aw: " Bernhard Bitsch
2020-07-05 8:44 ` Matthias Fischer
2020-07-05 8:44 ` Matthias Fischer [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=79d54d8a-bd99-6738-322e-d4f37cbbe5f8@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