public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dhcpcd: Update to 7.1.0
Date: Tue, 05 Feb 2019 12:01:42 +0000	[thread overview]
Message-ID: <15255694-E933-4D1D-B2D4-1CB7F0DF07D2@ipfire.org> (raw)
In-Reply-To: <20190204173844.8135-1-matthias.fischer@ipfire.org>

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

Thank you. Merged as well!

> On 4 Feb 2019, at 17:38, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> For some informations about this update see:
> https://roy.marples.name/blog/dhcpcd-7-1-0-released
> 
> "dhcpcd-7.1.0 has been released with the following changes:
> 
> - OpenBSD: works alongside slaacd(8)
> - NetBSD: sets SO_RERROR on to detect receive socket overflow
> - BSD: route improvements to avoid listening for own changes
> - Linux: use NETLINK_BROADCAST_ERROR
> - BSD: avoid late address deletion messages by testing address existance
> - IP6: implement IP6 address sharing
> - BSD: catch UP/DOWN events when interfaces does support media changes
> - IPv4LL: remember old address when carrier is lost
> 
> Many other minor fixes and documenation updates have been submitted by various
> community members for this release..."
> 
> Best,
> Matthias

You don’t have to sign your commit messages like this. Your name is at the top :)

> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/dhcpcd | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/dhcpcd b/lfs/dhcpcd
> index 9f3f5fbb6..cd940ae8b 100644
> --- a/lfs/dhcpcd
> +++ b/lfs/dhcpcd
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 7.0.8
> +VER        = 7.1.0
> 
> THISAPP    = dhcpcd-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 77bbb1d73b6f30d6ddcc8b0fd3eae266
> +$(DL_FILE)_MD5 = 918520b171f32f0da97316f3bcf3edc1
> 
> install : $(TARGET)
> 
> -- 
> 2.18.0
> 


      reply	other threads:[~2019-02-05 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 17:38 Matthias Fischer
2019-02-05 12:01 ` Michael Tremer [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=15255694-E933-4D1D-B2D4-1CB7F0DF07D2@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