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

Re: --simplify-merges breakage

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 8, 2013, 19:54 UTC
Message-ID
<7vfvz0x0gs.fsf@alter.siamese.dyndns.org>
In-Reply-To
<516313D3.2050309@bracey.fi>
Kevin Bracey <kevin@bracey.fi> writes:
Show 5 quoted lines
> Commit 4b7f53d ("simplify-merges: drop merge from irrelevant side
> branch") appears to have broken simplify-merges.
>
> ... now I see the "report problems
> immediately" message on the recent merge of that change.

I hope more people now see why we would like to see more people try 'next' regularly.

Will revert it for now, but that would mean side histories like gitk's will keep showing up in the simplified view.

Previous: Kevin Bracey
Message 2 of 2 in “--simplify-merges breakage”
  1. Kevin BraceyApr 8, 2013
  2. Junio C HamanoApr 8, 2013

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.