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

Re: git show-branch --topics and merge commits

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 18, 2011, 02:21 UTC
Message-ID
<7v8vrwl46q.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA+6x0LWXz-SpnZjdiV3UKJzUz3+0LiMOsbZHTn2gJ+v6bPGndA@mail.gmail.com>
Mike Shal <marfey@gmail.com> writes:
> So rev-list shows my merge commit and the 'new' commit, but
> show-branch --topics doesn't show 'new'. Is this the expected
> behavior?

Yes, show-branch was specifically written for people with strict sense of project hygiene who do not merge into their topic from upstream (which would turn the branch from "place to hold commits on this topic" into "place to hold commits on this topic and unrelated random changes made in upstream").

Previous: Mike ShalNext: Mike Shal
Message 2 of 5 in “git show-branch --topics and merge commits”
  1. Mike ShalJul 17, 2011
  2. Junio C HamanoJul 18, 2011
  3. Mike ShalJul 18, 2011
  4. Junio C HamanoJul 18, 2011
  5. Mike ShalJul 18, 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.