From owner-freebsd-ports-bugs@FreeBSD.ORG  Tue Feb 10 21:44:35 2015
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A8A2A94C
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 10 Feb 2015 21:44:35 +0000 (UTC)
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 8E808D2A
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 10 Feb 2015 21:44:35 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1ALiZsE022935
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 10 Feb 2015 21:44:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 196813] [NEW PORT] ports-mgmt/rubygem-mothra 0.0.3
Date: Tue, 10 Feb 2015 21:44:35 +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: pawel@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-196813-13-q5GcIFulFX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196813-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-196813-13@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-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 21:44:35 -0000

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

Pawel Pekala <pawel@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pawel@FreeBSD.org

--- Comment #5 from Pawel Pekala <pawel@FreeBSD.org> ---
XPORTNAME=    mothra
XPORTVERSION=    0.0.3
XCATEGORIES=    sysutils ruby

While this bug title suggests that this port should go in
ports-mgmt category something different is stated in CATEGORIES above.

In my opinion sysutils ruby is better category as our bugzilla is not
for ports only you can submit bugs in src and docs as well. So my
propositions is to put this port in sysutils/rubygem-mothra, agreed?

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