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

Re: [PATCH/RFC] Implemented return value for rev-list --quiet

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 26, 2011, 23:47 UTC
Message-ID
<7vpqo8bmn1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DB755D2.10303@boolsoft.org>
Jonas Gehring <jonas.gehring@boolsoft.org> writes:
Show 6 quoted lines
> Thank you for this explanation, this really cleared up the intended
> ... I wanted to use it for ancestry testing of two
> commits,...
>
> After some additional digging, I realized that git-merge-base is the
> right tool for my task.
Either
	test "$(git merge-base A B)" = "$(git rev-parse A)"
or
	test -z "$(git rev-list -1 A..B)"
would be valid ways to see if A is an ancestor of B.
Previous: Jonas Gehring
Message 4 of 4 in “Implemented return value for rev-list --quiet”
  1. Implemented return value for rev-list --quietJonas Gehring, Apr 26, 2011
  2. Junio C HamanoApr 26, 2011
  3. Jonas GehringApr 26, 2011
  4. Junio C HamanoApr 26, 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.