From owner-freebsd-questions Sat Apr 22 0:28:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 3D8E537B5D7 for ; Sat, 22 Apr 2000 00:28:37 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id BAA21795; Sat, 22 Apr 2000 01:29:21 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Sat, 22 Apr 2000 01:29:21 -0600 (CST) From: Ryan Thompson To: gerti-freebsdq@bitart.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: How to submit patch for GNU tar? In-Reply-To: <20000422072117.28824.qmail@camelot.bitart.com> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerd Knops wrote to freebsd-questions@FreeBSD.ORG: > Hi Everyone, > > [ ... ] > > A small patch (sample below) could avoid this: Read any > pending data from the pipe to gunzip before closing it. > > I am not absolutely sure however if that patch has side > effects in one of the many many modes gnutar supports. I'm not going to verify your patch, but I WILL recommend posting it to freebsd-hackers@freebsd.org so that someone will look at it, given that you are uncertain as to its side effects. When you are confident that your patch works (and/or an experienced bin hacker has given it the thumbs up), you will probably be asked to submit a PR including a problem description and your (possibly updated) patch. Use send-pr to submit the problem report and patch. Hope this helps, - Ryan -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message