From: Junio C Hamano Subject: Re: [PATCH 3/3] Teach cat-file a --quiet option Date: Sun, 22 Apr 2007 02:20:47 -0700 Message-ID: <7v8xckpxxs.fsf@assigned-by-dhcp.cox.net> References: <20070422011447.GC2910@spearce.org> <7virboq1tx.fsf@assigned-by-dhcp.cox.net> <20070422081556.GJ17480@spearce.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: "Shawn O. Pearce" X-From: git-owner@vger.kernel.org Sun Apr 22 11:20:55 2007 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1HfYFY-0001hK-Es for gcvg-git@gmane.org; Sun, 22 Apr 2007 11:20:52 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965632AbXDVJUt (ORCPT ); Sun, 22 Apr 2007 05:20:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965626AbXDVJUt (ORCPT ); Sun, 22 Apr 2007 05:20:49 -0400 Received: from fed1rmmtao105.cox.net ([68.230.241.41]:36302 "EHLO fed1rmmtao105.cox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965620AbXDVJUs (ORCPT ); Sun, 22 Apr 2007 05:20:48 -0400 Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao105.cox.net (InterMail vM.7.05.02.00 201-2174-114-20060621) with ESMTP id <20070422092048.IVTC1266.fed1rmmtao105.cox.net@fed1rmimpo02.cox.net>; Sun, 22 Apr 2007 05:20:48 -0400 Received: from assigned-by-dhcp.cox.net ([68.5.247.80]) by fed1rmimpo02.cox.net with bizsmtp id q9Ln1W00E1kojtg0000000; Sun, 22 Apr 2007 05:20:47 -0400 In-Reply-To: <20070422081556.GJ17480@spearce.org> (Shawn O. Pearce's message of "Sun, 22 Apr 2007 04:15:56 -0400") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: "Shawn O. Pearce" writes: > Junio C Hamano wrote: >> "Shawn O. Pearce" writes: >> > This is especially true if the script is using something like >> > `cat-file blob HEAD:path/to/file` to look at an optional file's >> > content. >> >> I am not sure if I agree with this logic. How is this different >> from discarding stderr to /dev/null? > > Also, a redirect of stderr to /dev/null kills other error messages > that might be interesting to see on stderr of the caller,... I think that quite depends on what your definition of "other" is; see my other message on this subject.