From owner-freebsd-ports-bugs@freebsd.org  Wed Apr 20 10:58:04 2016
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 B9A73B16DD3
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Wed, 20 Apr 2016 10:58:04 +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 A9B851ADC
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 20 Apr 2016 10:58:04 +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 u3KAw4mP031218
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 20 Apr 2016 10:58:04 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 208634] databases/mysql57-{server,client}: Fix regression in
 r412723
Date: Wed, 20 Apr 2016 10:58:04 +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 Many People
X-Bugzilla-Who: mokhi64@gmail.com
X-Bugzilla-Status: In Progress
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-208634-13-8M5tI5YBc1@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208634-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-208634-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.21
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: Wed, 20 Apr 2016 10:58:04 -0000

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

--- Comment #12 from Mahdi Mokhtari <mokhi64@gmail.com> ---
(In reply to Markus Kohlmeyer from comment #11)
I think it's better we don't make a spaghetti issue :) [how ever, maybe the
other patches are better in some cases].
I myself think as long as the patch doesn't change anything on the user view
(nor fixing critical issue), let's make it go forward as planned, and do
optimizing things in separate issue. (this also reduces our work in generat=
ing
new patches against always changing HEAD :D)

What's your opinion, guys ?

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