From owner-freebsd-ports-bugs@freebsd.org  Tue Apr 18 21:02:58 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02F8FD4452F
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Tue, 18 Apr 2017 21:02:58 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E64E6FF8
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 18 Apr 2017 21:02:57 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3IL2uA2018556
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 18 Apr 2017 21:02:57 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 218616] dns/opendnssec13: Pull in textproc/gnugrep for a proper
 grep(1) with GNU extensions
Date: Tue, 18 Apr 2017 21:02:57 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: bsdports@kyle-evans.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-218616-13-rqRaVDswiQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-218616-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-218616-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 21:02:58 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218616

--- Comment #2 from Kyle Evans <bsdports@kyle-evans.net> ---
(In reply to jaap from comment #1)

Hello!

Thank you for your response and feedback. =3D) It probably is a good idea f=
or
this to get applied anyways, given how quarterlies work out and whatnot -- =
I'd
rather not get you notified of breakage on a port that's supposed to be goi=
ng
away when the change does come.

--=20
You are receiving this mail because:
You are the assignee for the bug.=