From owner-freebsd-ports@freebsd.org Wed Dec 9 00:19:24 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5585C4B01F5 for ; Wed, 9 Dec 2020 00:19:24 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CrHjR6G7Rz3Lw1 for ; Wed, 9 Dec 2020 00:19:23 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 0B90JPbr025891 for ; Tue, 8 Dec 2020 16:19:31 -0800 (PST) (envelope-from portmaster@bsdforge.com) MIME-Version: 1.0 Date: Tue, 08 Dec 2020 16:19:25 -0800 From: Chris To: freebsd-ports@freebsd.org Subject: Re: Bug 251656 In-Reply-To: <20201208133315.1a3a1309@bigus.dream-tech.com> References: <20201208133315.1a3a1309@bigus.dream-tech.com> User-Agent: UDNSMS/17.0 Message-ID: X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CrHjR6G7Rz3Lw1 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2020 00:19:24 -0000 On 2020-12-08 13:33, Dave Hayes wrote: > Is there a method for getting this assigned? I'll admit I misspelled the > port > name in the subject, but now how do I fix the process? Thanks in advance. If you opened the bug. You should have the permission to rewrite the topic of the bug. So that it's gets assigned, and addressed more promptly. :-)00 FYI ideally, the topic should have read: x11-servers/xorg-server: segmentation fault Seems insignificant. But the colon is significant. HTH --Chris