From owner-freebsd-hackers Tue May 9 21:45: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id CD75837B6C5 for ; Tue, 9 May 2000 21:44:57 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id XAA24550; Tue, 9 May 2000 23:43:23 -0500 (CDT) (envelope-from dan) Date: Tue, 9 May 2000 23:43:22 -0500 From: Dan Nelson To: Garance A Drosihn Cc: hackers@FreeBSD.ORG Subject: Re: PR's and patches Message-ID: <20000509234322.A18368@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.14i In-Reply-To: ; from "Garance A Drosihn" on Tue May 9 21:40:02 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 09), Garance A Drosihn said: > Awhile ago I submitted a PR with a patch in it. Today I was thinking > that I would clean it up, and since I didn't keep a copy of the > earlier patch I thought I would get it from the PR. > > I used 'lynx' to download the PR, and it seemed to come down > correctly (tab-characters where I'd expect them, etc), but the patch > did not apply. Turned out that because I was going thru a web > interface, things like '<', '>', and '&' were changed to html-safe > equivalents. Good for HTML, bad for C. > > So, my dumb question is, how DO you pull patches out of a PR? The best way is to fetch the PR through a protocol that doesn't force you to escape characters :) I can't find the gnats database on ftp.freebsd.org, so your only solution would probably be to cvsup the gnats collection (130 MB though). A quick hack to get a single patch downloaded cleanly would be to load lynx up on the page, and P)rint it to a local file. Then patch -l should work. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message