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

Re: git log --quiet bug?

From
Jeff King <peff@peff.net>
Date
Nov 9, 2011, 00:59 UTC
Message-ID
<20111109005927.GA25876@sigill.intra.peff.net>
In-Reply-To
<7vy5vqw47x.fsf@alter.siamese.dyndns.org>
On Tue, Nov 08, 2011 at 04:04:50PM -0800, Junio C Hamano wrote:
Show 13 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > Try:
> >
> >   test -z "$(git rev-list -1 origin..HEAD)" &&
> >   echo nothing that needs pushing
> >
> > You can also use --count to get the exact number, but if you just care
> > whether there is something or nothing, using "-1" lets git stop the
> > graph traversal immediately.
> 
> Doesn't some variant of "branch -v" show the ahead/behind information for
> all branches?

Yeah, but I thought the question was how to figure this out programatically in a script.

-Peff
Previous: Junio C Hamano
Message 6 of 6 in “git log --quiet bug?”
  1. Prasad DeshpandeNov 8, 2011
  2. Jeff KingNov 8, 2011
  3. Junio C HamanoNov 8, 2011
  4. Jeff KingNov 8, 2011
  5. Junio C HamanoNov 9, 2011
  6. Jeff KingNov 9, 2011

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.