From owner-freebsd-ports-bugs@freebsd.org  Tue Mar  8 16:44:12 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 4F275AC8A24
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Tue,  8 Mar 2016 16:44:12 +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 3FE3FF90
 for <freebsd-ports-bugs@FreeBSD.org>; Tue,  8 Mar 2016 16:44:12 +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 u28GiBK3078150
 for <freebsd-ports-bugs@FreeBSD.org>; Tue, 8 Mar 2016 16:44:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 207810] [NEW PORT] ports-mgmt/portest: Patch file automation
 for FreeBSD-ports
Date: Tue, 08 Mar 2016 16:44:12 +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: easy, patch-ready
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: portmaster@bsdforge.com
X-Bugzilla-Status: New
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-207810-13-CgNC2HrfZ1@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207810-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-207810-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: Tue, 08 Mar 2016 16:44:12 -0000

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

--- Comment #6 from Chris Hutchinson <portmaster@bsdforge.com> ---
(In reply to Torsten Z=C3=BChlsdorff from comment #4)
> (In reply to Chris Hutchinson from comment #3)
>=20
> > Doesn't bugzilla know that shar(1) files are of text/plain?
>=20
> I must protect bugzilla, because it did it right. I declared the mime type
> "application/x-shar". Often the browser itself does not know, that you can
> view this as text and offers a download of this file.
Yes. You can never trust those evil text/plain files. ;)
>=20
> Of course you can teach your browser to do this. But first it is very
> annoying :D
Aren't you the clever one. See how you just made
this *my* responsibility. ;) ;)

Point taken. Thanks, Torsten!

--Chris

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