From owner-cvs-src@FreeBSD.ORG Fri May 4 15:03:29 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3003E16A402; Fri, 4 May 2007 15:03:29 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id D148413C469; Fri, 4 May 2007 15:03:28 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l44F3NH7054308; Fri, 4 May 2007 08:03:24 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <463B4B3B.8080209@freebsd.org> Date: Fri, 04 May 2007 08:03:23 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <200705030433.l434XBvW005733@repoman.freebsd.org> <46397035.7000606@freebsd.org> <463A19D6.6070400@freebsd.org> <20070504141545.8mis6w94gocw8408@webmail.leidinger.net> In-Reply-To: <20070504141545.8mis6w94gocw8408@webmail.leidinger.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Colin Percival Subject: Re: cvs commit: src/usr.bin/tar write.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2007 15:03:29 -0000 >>> I wonder if it would be simpler to set non-zero exit only >>> if this is the first path returned from tree_next() ... >> >> Hmm... I considered this, but I wasn't sure if there were any edge >> cases where the first path returned by tree_next might not be the >> path passed to tree_open; so I decided to take the route which I >> knew would always work. > > What if someone gives more than one path to tar? The function in question (write_heirarchy) is called once for each command-line argument. Tim Kientzle