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

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

From
JGJonas Gehring <jonas.gehring@boolsoft.org>
Date
Apr 26, 2011, 23:31 UTC
Message-ID
<4DB755D2.10303@boolsoft.org>
In-Reply-To
<7vwrigbor6.fsf@alter.siamese.dyndns.org>
On 04/27/2011 01:02 AM, Junio C Hamano wrote:
> Given two commits A and X, "rev-list --objects A..X" is a way to make sure
> that everything between A and X exists.

Thank you for this explanation, this really cleared up the intended usage of --quiet for me. I wanted to use it for ancestry testing of two commits, noticed the hard-coded return value of '0' in cmd_rev_list() and thought that the implementation is probably missing.

After some additional digging, I realized that git-merge-base is the right tool for my task.

Regards, Jonas

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.