From owner-freebsd-hackers Fri Mar 19 14:13: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C7D2E14ED5 for ; Fri, 19 Mar 1999 14:12:55 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id RAA34406; Fri, 19 Mar 1999 17:14:16 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: Date: Fri, 19 Mar 1999 17:13:06 -0500 To: Julian Elischer , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Exctracting stuff from PRs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:08 AM -0800 3/19/99, Julian Elischer wrote: > Sometimes people submit code in a PR (in fact we encourage this). > Unfortunately they often include the code as an attachment, > so it appears in the PR database as some 'encoded' form of data. When I went to use 'send-pr' for a problem, I was surprised that send-pr itself does not have a parameter for "sample file" or some-such. If it did, then you would have some control of what format that enclosure arrived in. I was going to suggest that at the time, but then I thought "Hey, I could write a sample implementation, and thus I would be doing more than just asking someone else to do work". Of course, I only think of it when I'm *doing* a send-pr, and so far I've never remembered to actually sit down and write a change to the send-pr script. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message