From owner-freebsd-python@freebsd.org  Tue Jun 30 05:55:19 2015
Return-Path: <owner-freebsd-python@freebsd.org>
Delivered-To: freebsd-python@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 42662990D9D
 for <freebsd-python@mailman.ysv.freebsd.org>;
 Tue, 30 Jun 2015 05:55:19 +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 2EF5F1EFC
 for <freebsd-python@FreeBSD.org>; Tue, 30 Jun 2015 05:55:19 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5U5tJ73010772
 for <freebsd-python@FreeBSD.org>; Tue, 30 Jun 2015 05:55:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-python@FreeBSD.org
Subject: [Bug 201182] lang/python27 needs aarch64 handler
Date: Tue, 30 Jun 2015 05:55:19 +0000
X-Bugzilla-Reason: CC
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: easy, needs-patch, needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: koobs@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: sbruno@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback+
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-201182-17421-8d44rTVamz@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201182-17421@https.bugs.freebsd.org/bugzilla/>
References: <bug-201182-17421@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2015 05:55:19 -0000

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

--- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> ---
(In reply to Philip M. Gollucci from comment #4)

My feelings when I asked Sean to create a review were:

* I could only review the change syntactically, so opening it up to broader
review was good for semantic review
* Phab reviews are likely to get more visibility, thus progress quicker if it
goes to python@ for review
* (Documented) Code Review is a good habit to get into
* Sean could commit it directly (encourages cross-repo fetilization) with
approval, thus less gating/blocking then assigning it to an individual and
waiting for them to commit it.

TL:DR, Quicker outcome, less blocking.

-- 
You are receiving this mail because:
You are on the CC list for the bug.