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

Re: Visualizing merge conflicts after the fact (using kdiff3)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 18, 2015, 13:05 UTC
Message-ID
<126a1ed453d1624083c069b904dd25c0@www.dscho.org>
In-Reply-To
<5582B8EC.1060205@drmicha.warpmail.net>
Hi Micha,
On 2015-06-18 14:26, Michael J Gruber wrote:
Show 14 quoted lines
> Johannes Schindelin venit, vidit, dixit 16.06.2015 11:43:
>
>> To list all the merge commits in the current branch, I would use the command-line:
>>
>> ```bash
>> git rev-list --author="My Colleague" --parents HEAD |
>> sed -n 's/ .* .*//p'
>> ```
>>
>> (i.e. listing all the commits with their parents, then filtering just the ones having more than one parent, which would include octopus merges if your history has them.)
> 
> :)
> 
> "--merges" (aka "--min-parents=2") is your friend here.
Learnt something!

Thanks, Dscho

Previous: Michael J GruberNext: Junio C Hamano
Message 5 of 9 in “Visualizing merge conflicts after the fact (using kdiff3)”
  1. Eric RaibleJun 16, 2015
  2. Johannes SchindelinJun 16, 2015
  3. Eric RaibleJun 16, 2015
  4. Michael J GruberJun 18, 2015
  5. Johannes SchindelinJun 18, 2015
  6. Junio C HamanoJun 18, 2015
  7. Michael J GruberJun 19, 2015
  8. Junio C HamanoJun 19, 2015
  9. Sebastian SchuberthJul 6, 2015

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.