From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dhcpcd: Update to 9.1.3
Date: Sat, 04 Jul 2020 10:32:14 +0100 [thread overview]
Message-ID: <181D6533-77ED-459D-8AE6-069B2DBDD4A7@ipfire.org> (raw)
In-Reply-To: <b7fbe1e0-58f6-34c0-5850-3c9dce570c1f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
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 9:32 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 [this message]
2020-07-04 10:23 ` Aw: " Bernhard Bitsch
2020-07-05 8:44 ` 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=181D6533-77ED-459D-8AE6-069B2DBDD4A7@ipfire.org \
--to=michael.tremer@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