git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/3] rev-list: Introduce --no-output to avoid /dev/null redirects

From
Alex Riesen <raa.lkml@gmail.com>
Date
Nov 8, 2007, 23:44 UTC
Message-ID
<20071108234418.GE4899@steel.home>
In-Reply-To
<20071108080052.GB16690@spearce.org>
Shawn O. Pearce, Thu, Nov 08, 2007 09:00:52 +0100:
Show 7 quoted lines
> Some uses of git-rev-list are to run it with --objects to see if
> a range of objects between two or more commits is fully connected
> or not.  In such a case the caller doesn't care about the actual
> object names or hash hints so formatting this data only for it to
> be dumped to /dev/null by a redirect is a waste of CPU time.  If
> all the caller needs is the exit status then --no-output can be
> used to bypass the commit and object formatting.
We already have --quiet and even --exit-code.
Previous: Shawn O. PearceNext: Junio C Hamano
Message 2 of 6 in “rev-list: Introduce --no-output to avoid /dev/null redirects”
  1. 2/3 rev-list: Introduce --no-output to avoid /dev/null redirectsShawn O. Pearce, Nov 8, 2007
  2. Alex RiesenNov 8, 2007
  3. Junio C HamanoNov 9, 2007
  4. Alex RiesenNov 9, 2007
  5. Junio C HamanoNov 9, 2007
  6. Shawn O. PearceNov 9, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.