From owner-svn-src-head@freebsd.org Tue Dec 5 15:35:28 2017 Return-Path: Delivered-To: svn-src-head@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 2C0C5E6DDBF; Tue, 5 Dec 2017 15:35:28 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from shxd.cx (mail.shxd.cx [64.201.244.140]) (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 1C2247F2F1; Tue, 5 Dec 2017 15:35:28 +0000 (UTC) (envelope-from devin@shxd.cx) Received: from [64.201.244.132] (port=54578 helo=[10.0.0.109]) by shxd.cx with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1eMFFl-000MC9-FN; Tue, 05 Dec 2017 15:35:25 +0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Devin Teske Mime-Version: 1.0 (1.0) Subject: Re: svn commit: r326554 - in head: . usr.bin/sponge usr.bin/sponge/tests usr.bin/tee Date: Tue, 5 Dec 2017 07:33:21 -0800 Message-Id: References: <201712051258.vB5CwjQN051356@pdx.rh.CN85.dnsmgr.net> <22918eec-4c98-01e4-4c63-e145fbc6eab9@selasky.org> Cc: rgrimes@freebsd.org, cem@freebsd.org, Eitan Adler , src-committers , svn-src-all@freebsd.org, svn-src-head@freebsd.org In-Reply-To: <22918eec-4c98-01e4-4c63-e145fbc6eab9@selasky.org> To: Hans Petter Selasky X-Mailer: iPhone Mail (13G36) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2017 15:35:28 -0000 > On Dec 5, 2017, at 5:00 AM, Hans Petter Selasky wrote: >=20 >> On 12/05/17 13:58, Rodney W. Grimes wrote: >> Further more, why does freebsd need this in base? >=20 > Hi, >=20 > I think this is useful. It could replace the "-i " (intermediate) option f= or "sed" for example. It avoids creating temporary files when filtering file= s, right? >=20 > --HPS >=20 Wth is wrong with: data=3D$( sed -e '...' somefile ) && echo "$data" > somefile or set -e data=3D... echo "$data" > ... or exec 3< ... <&3 or (I digress) Infinite variations, but the gist is that sponge looks to be trying to help s= h(1)/similar when help is unneeded. Why buffer data into memory via fork-exec-pipe to sponge when you can buffer= to native namespace without pipe to sponge? Am I missing something? Why do we need sponge(1)? --=20 Devin=