From owner-freebsd-amd64@freebsd.org Fri May 27 00:23:52 2016 Return-Path: Delivered-To: freebsd-amd64@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 D3059B4B9E2 for ; Fri, 27 May 2016 00:23:52 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4CEC1EE2 for ; Fri, 27 May 2016 00:23:52 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u4R00eJZ097990 for ; Thu, 26 May 2016 17:00:46 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: , From: "Chris H" Subject: Re: [Bug 209758] Broadcom 5717 C not working Date: Thu, 26 May 2016 17:00:46 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <5137f082c2a90fc2f4df36f4e1e39238@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 00:23:52 -0000 On Thu, 26 May 2016 20:52:52 +0000 bugzilla-noreply@freebsd.org wrote > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209758 > > --- Comment #9 from Giuliano --- > Dear Ngie, > > I have triple checked typing to be sure it is not my mistake. There is a > error: fetch: No match fetch(1) is tripping on the question mark " ? " in the URL you were given. you're likely using (t)csh for your shell. You'll need to quote the URL. Try this: cd /usr/src fetch -o - 'https://bz-attachments.freebsd.org/attachment.cgi?id=170681' | patch -p1 Make *sure* that the fetch line is all on one line. I say that because your mail client may wrap that line. > Hmm... I can't seem to find a patch in there > anywhere. > > Best regards, > Giuliano > --Chris