From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Aug 17 10:40:12 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B94D106564A for ; Wed, 17 Aug 2011 10:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9C88FC1A for ; Wed, 17 Aug 2011 10:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p7HAeBVw021304 for ; Wed, 17 Aug 2011 10:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p7HAeB6g021303; Wed, 17 Aug 2011 10:40:11 GMT (envelope-from gnats) Date: Wed, 17 Aug 2011 10:40:11 GMT Message-Id: <201108171040.p7HAeB6g021303@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Chris Rees Cc: Subject: Re: ports/159828: [MAINTAINER] www/ap22-mod_gnutls: update to 0.5.10 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Chris Rees List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 10:40:12 -0000 The following reply was made to PR ports/159828; it has been noted by GNATS. From: Chris Rees To: bug-followup@FreeBSD.org, fumifumi@abacustech.jp, linimon@FreeBSD.org Cc: Subject: Re: ports/159828: [MAINTAINER] www/ap22-mod_gnutls: update to 0.5.10 Date: Wed, 17 Aug 2011 11:39:40 +0100 Hi Fumiyuki, I've investigated the cause of Edwin's auto-assignment bot's confusion over your email address, and I've discovered that it's because your address as appears in the raw email Fumiyuki Shimizu =?iso-2022-jp?B?GyRCQDY/ZUo4OVQbKEI=?= has been wrapped, so that your address is below the From: line. Unfortunately I can't see an easy way to compensate for that, so unless anyone else has any better ideas the easiest way to ensure that your PRs don't get messed up by the tool is to try to reduce the number of characters you have before your email address when using send-pr. If that's a big problem then we can just keep fixing the class manually for you. Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.