From: Junio C Hamano <gitster@pobox.com>
To: Emily Shaffer <nasamuffin@google.com>
Cc: Aditya Garg <gargaditya08@live.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Add git imap-get-recipients command
Date: Thu, 22 May 2025 11:55:00 -0700 [thread overview]
Message-ID: <xmqqplg05vcr.fsf@gitster.g> (raw)
In-Reply-To: <CAJoAoZm_fsfhq2gD4JVCihf5do-+CurFRBfw8PX8-0QbSKk-VA@mail.gmail.com> (Emily Shaffer's message of "Thu, 22 May 2025 10:54:22 -0700")
Emily Shaffer <nasamuffin@google.com> writes:
> Definitely I don't believe Junio's point was "don't send us this
> patch, I don't care" - but rather "how do we know we care until we see
> how you've implemented it".
Thanks for clarification.
Even without an implementation, a clear description of design (no, a
design document on large swath of paper is often not what you want
to come up with, as there clearly is a chicken-and-egg problem to
convince others that the design is worth taking a look) would help.
prev parent reply other threads:[~2025-05-22 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 19:23 Add git imap-get-recipients command Aditya Garg
2025-05-21 19:52 ` Junio C Hamano
2025-05-22 1:52 ` Junio C Hamano
2025-05-22 3:20 ` Aditya Garg
2025-05-22 17:54 ` Emily Shaffer
2025-05-22 17:59 ` Aditya Garg
2025-05-22 18:55 ` Junio C Hamano [this message]
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=xmqqplg05vcr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=gargaditya08@live.com \
--cc=git@vger.kernel.org \
--cc=nasamuffin@google.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).