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

Re: bug with git merge-base

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Sep 21, 2018, 02:31 UTC
Message-ID
<CAPig+cS+8+uGQTfxmq1XGMt5FBM1oq72d3N=3BkjhrA9ui+EWw@mail.gmail.com>
In-Reply-To
<CA+KyZp4G6WCXjp_9x+NBWZysfg+Fu_PtF4qrhipT8UuLNnsCHA@mail.gmail.com>

On Wed, Sep 19, 2018 at 6:25 PM Alexander Mills <alexander.d.mills@gmail.com> wrote:

Show 6 quoted lines
> The following command sequence exits with 1, and no stderr
>
> base='remotes/origin/dev';
> fork_point="$(git merge-base --fork-point "$base")";
>
> I cannot figure out why it's exiting with 1, but there is no stdout/stderr
Unable to reproduce the problem. Perhaps you can provide more context.
Previous: Alexander MillsNext: Junio C Hamano
Message 2 of 4 in “bug with git merge-base”
  1. Alexander MillsSep 19, 2018
  2. Eric SunshineSep 21, 2018
  3. Junio C HamanoSep 21, 2018
  4. Junio C HamanoSep 21, 2018

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.