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

Re: BUG: git pull --rebase on detatched head prints a lot of usage warnings

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 3, 2010, 22:31 UTC
Message-ID
<7vy686lc82.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTimgk-jqyKD+ab=bHZLVH3F52WqCjr4v3chMY_Fv@mail.gmail.com>
Santi Béjar <santi@agolina.net> writes:
> No, I'm not sure. In fact the documentation explicit says that they
> are different. But I fail to see when it matters, and more
> specifically (now that I've reread the docs), what is the point of
> "merge-base A B C".

See c5dc9a2 (git-merge-octopus: use (merge-base A (merge B C D E...)) for stepwise merge, 2008-07-27), not the patch but the explanation.

> Just a data point, show-branch --merge-base is only used once in the
> code, in git-pull.sh, but "git merge-base A B C" is not used (at least
> using my grep).

Your grep skill needs honing ;-) The variable MRC in git-merge-octopus is a space separated list of commit object names, split at $IFS when merge-base is called.

Previous: Santi Béjar
Message 8 of 8 in “BUG: git pull --rebase on detatched head prints a lot of usage warnings”
  1. Sverre RabbelierDec 3, 2010
  2. Jonathan NiederDec 3, 2010
  3. Sverre RabbelierDec 3, 2010
  4. Santi BéjarDec 3, 2010
  5. Sverre RabbelierDec 3, 2010
  6. Junio C HamanoDec 3, 2010
  7. Santi BéjarDec 3, 2010
  8. Junio C HamanoDec 3, 2010

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.