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

Re: I just pulled, and git log --graph does not show all

From
UBUwe Brauer <oub@mat.ucm.es>
Date
Oct 9, 2019, 14:06 UTC
Message-ID
<87a7aaovxg.fsf@mat.ucm.es>
In-Reply-To
<20191009132345.GH29845@szeder.dev>
   > Anyway, in your first email you asked how you can merge that branch
   > into 'master'.  The command 'git merge origin/strings' will "merge" it
   > without actually creating a merge commit, because 'strings' builds
   > entirely on top of 'master'; this is what Git calls a "fast-forward
   > merge".  If you do want a merge commit, then run 'git merge --no-ff
   > origin/strings'.

Interestingly enough it is impossible in mercurial to have a (not ff) merge in mercurial in this situation, because you have only one head (linear history) and two bookmarks. That is one thing I dislike in mercurial, but it can be easily avoided by using named branches or topics, but any way this is off topic.

Previous: Uwe Brauer
Message 7 of 7 in “I just pulled, and git log --graph does not show all”
  1. Uwe BrauerSep 24, 2019
  2. SZEDER GáborOct 8, 2019
  3. Uwe BrauerOct 9, 2019
  4. Derrick StoleeOct 9, 2019
  5. SZEDER GáborOct 9, 2019
  6. Uwe BrauerOct 9, 2019
  7. Uwe BrauerOct 9, 2019

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.