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

Re: Git merge conflicts and encoding of logs

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Dec 23, 2008, 08:41 UTC
Message-ID
<4950A422.5030100@viscovery.net>
In-Reply-To
<7vprjjfgi7.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
Show 12 quoted lines
> <<<<<<< HEAD:foo
> これはサイドブランチの変更です。
> やはり JIS コードで書いてます。
> =======
> 日本語のファイルです。
> JIS コードで書いてます。
>>>>>>>> master:foo
> 
> The above will probably come out as UTF-8 in this mail text, but the point
> is that the confict side markers do not have anything but filename and the
> branch name.  I am still scratching my head trying to see where in the
> merge-recursive codepath you got snippet of log message.

Try rebase -i instead of merge: This should put summary lines onto the conflict markers.

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 5 in “Git merge conflicts and encoding of logs”
  1. Junichi UekawaDec 23, 2008
  2. Junio C HamanoDec 23, 2008
  3. Johannes SixtDec 23, 2008
  4. Junio C HamanoDec 23, 2008
  5. Junichi UekawaDec 23, 2008

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.