From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "tobias.boesch@miele.com" <tobias.boesch@miele.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: fix history window panes position
Date: Fri, 05 Dec 2025 11:23:11 +0900 [thread overview]
Message-ID: <xmqq5xal8y5s.fsf@gitster.g> (raw)
In-Reply-To: <9f7af47a-ae39-4931-805d-f6e4549231ac@kdbg.org> (Johannes Sixt's message of "Thu, 4 Dec 2025 10:20:52 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
> 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.
next prev parent reply other threads:[~2025-12-05 2:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 13:08 [PATCH] gitk: fix history window panes position tobias.boesch
2025-12-03 9:35 ` AW: " tobias.boesch
2025-12-03 10:15 ` Johannes Sixt
2025-12-04 8:39 ` AW: " tobias.boesch
2025-12-04 9:20 ` Johannes Sixt
2025-12-05 2:23 ` Junio C Hamano [this message]
2025-12-05 6:40 ` Johannes Sixt
2025-12-05 7:22 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5xal8y5s.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=tobias.boesch@miele.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).