From: Junio C Hamano <gitster@pobox.com>
To: Matthew Hughes <matthewhughes934@gmail.com>
Cc: Matthew Hughes via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] userdiff: add builtin diff driver for TypeScript language
Date: Tue, 16 Jul 2024 14:10:24 -0700 [thread overview]
Message-ID: <xmqqjzhl6o1r.fsf@gitster.g> (raw)
In-Reply-To: <20240716193344.bjb62zsfnrfw3ngf@archP14s> (Matthew Hughes's message of "Tue, 16 Jul 2024 20:33:44 +0100")
Matthew Hughes <matthewhughes934@gmail.com> writes:
> I'm leaning towards the former case: that this patch was premature.
OK. Then let's take sufficient time. After all, we are never in a
hurry ;-)
Thanks for giving an honest assessment. Will keep the topic in
'seen' without marking it for 'next' (at least until it gets
replaced with a version that is more suitable to the public).
next prev parent reply other threads:[~2024-07-16 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 16:33 [PATCH] userdiff: add builtin diff driver for TypeScript language Matthew Hughes via GitGitGadget
2024-07-16 12:21 ` Matthew Hughes
2024-07-16 15:45 ` Junio C Hamano
2024-07-16 19:33 ` Matthew Hughes
2024-07-16 21:10 ` Junio C Hamano [this message]
2024-07-16 20:53 ` Johannes Sixt
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=xmqqjzhl6o1r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=matthewhughes934@gmail.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 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.