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

Re: [PATCH] gitk: fix history window panes position

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 5, 2025, 02:23 UTC
Message-ID
<xmqq5xal8y5s.fsf@gitster.g>
In-Reply-To
<9f7af47a-ae39-4931-805d-f6e4549231ac@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 5 quoted lines
> BTW, the email that I received was not usable for git-am because its
> body was base64-encoded. I had to copy the text from my MUA to a text
> file before I could apply it with git-am. If you have trouble sending
> out unencoded, raw text mails, please use Gitgitgadget if there is more
> than one patch in the series.

"git am" (actually "git mailsplit" that is called from it to extract what can be used by "git apply") should be able to deal with

    Content-Type: text/plain; charset="utf-8"
    Content-Transfer-Encoding: base64
so there may be something else going on.  The rendition at lore
https://lore.kernel.org/git/AM0PR08MB5426BC141388A69BB5087732E1D8A@AM0PR08MB5426.eurprd08.prod.outlook.com/

seems to show that it has in-body headers that should have been moved to e-mail headers, but otherwise it looks more or less like legit patch e-mail without anything unusual. It could be the patch may be full of ^M, but we cannot tell from the way lore/public-inbox shows its messages.

Previous: Johannes SixtNext: Johannes Sixt
Message 6 of 8 in “gitk: fix history window panes position”
  1. gitk: fix history window panes positiontobias.boesch@miele.com, Dec 2, 2025
  2. AW: [PATCH] gitk: fix history window panes positiontobias.boesch@miele.com, Dec 3, 2025
  3. Johannes SixtDec 3, 2025
  4. AW: [PATCH] gitk: fix history window panes positiontobias.boesch@miele.com, Dec 4, 2025
  5. Johannes SixtDec 4, 2025
  6. Junio C HamanoDec 5, 2025
  7. Johannes SixtDec 5, 2025
  8. Junio C HamanoDec 5, 2025

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.