All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andrew Carter <andrew@emailcarter.com>
Cc: git@vger.kernel.org,  "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v2] docs: indicate http.sslCertType and sslKeyType
Date: Wed, 05 Feb 2025 09:45:57 -0800	[thread overview]
Message-ID: <xmqqy0yknv3e.fsf@gitster.g> (raw)
In-Reply-To: <8f9a3a2b-dfa2-4ff4-9f97-e65404315396@emailcarter.com> (Andrew Carter's message of "Tue, 4 Feb 2025 23:46:21 -0600")

Andrew Carter <andrew@emailcarter.com> writes:

> On 1/30/25 4:22 PM, Junio C Hamano wrote:
>
>> I thought that the initial iteration I received from you on Jan 23rd
>> was just fine.  Did you change some settings with your MUA?  The patch
>> is heavily whitespace damaged, with full of &nbsp;.
> ...
> Sorry for the inconvenience, and thanks for your patience.
>
> The original message was composed by GitGitGadget. I pasted the v2
> patch into Thunderbird initially, which clearly failed.
>
> I sent a new v2 patch using git send-email, and at a glance it looks
> unbroken.
>
> If further changes are needed I can get an updated patch to you with a
> faster turnaround now.

Thanks for your patience, too.

E-mailed patch workflow is easy for automation, once set-up
correctly, but there is certain entry cost.

Queued.  Let's mark it for 'next'.


  reply	other threads:[~2025-02-05 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  0:16 [PATCH] docs: indicate http.sslCertType and sslKeyType Andrew Carter via GitGitGadget
2025-01-23  0:34 ` brian m. carlson
2025-01-23 17:43   ` Junio C Hamano
2025-01-25  6:38     ` Andrew Carter
2025-01-30 13:18 ` [PATCH v2] " Andrew Carter
2025-01-30 22:22   ` Junio C Hamano
2025-02-05  5:46     ` Andrew Carter
2025-02-05 17:45       ` Junio C Hamano [this message]
2025-02-05  5:38 ` Andrew Carter

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=xmqqy0yknv3e.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=andrew@emailcarter.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.