From: Junio C Hamano <email@example.com>
To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>
Cc: Skrab Sah <email@example.com>, firstname.lastname@example.org
Subject: Re: what if i use makeheader tool to generate c header file, it would be accepted.
Date: Mon, 19 Sep 2022 10:40:45 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (=?utf-8?B?IsOG?= =?utf-8?B?dmFyIEFybmZqw7Zyw7A=?= Bjarmason"'s message of "Mon, 19 Sep 2022 12:45:06 +0200")
Ævar Arnfjörð Bjarmason <email@example.com> writes:
> On Mon, Sep 19 2022, Skrab Sah wrote:
> Just sending a $subject is rather light on details, so I'm having to do
> a lot of guessing, but here goes.
> In case this is a genuine "prep question" that you're asking in
> wonderining if you should even waste time on coming up with a patch to
> do $subject I want to say that:
> Now, this does *not* mean that we're not interested, but just that we're
> very big on a "show your work" approach to things.
Perhaps this should be made into a FAQ entry?
In general, we do not give promises or guidance, but something a
contributor finds it rewarding to work on, whether we would leter
accept in the upstream, will spread among users and developers, and
eventually we would come begging to the contributor for upstreaming.
On the other hand, a new thing that the contributor who thought of
does not feel it is worth investing their work in, if only to use
for themselves, is unlikely to be of interest to us.
So saying "if this will be accepted, I'll work on it" is counter
productive, as it is easily (mis)taken as a sign that it is the
In other words, make it so good that we would come to you.
next prev parent reply other threads:[~2022-09-19 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 7:14 what if i use makeheader tool to generate c header file, it would be accepted Skrab Sah
2022-09-19 10:45 ` Ævar Arnfjörð Bjarmason
2022-09-19 17:40 ` Junio C Hamano [this message]
2022-09-20 8:40 ` Skrab Sah
2022-09-20 9:58 ` Ævar Arnfjörð Bjarmason
2022-09-21 7:53 ` Skrab Sah
2022-09-21 8:11 ` Đoàn Trần Công Danh
2022-09-21 8:46 ` Skrab Sah
2022-09-23 7:28 ` Ævar Arnfjörð Bjarmason
2022-09-24 8:19 ` Skrab Sah
2022-09-21 16:28 ` Junio C Hamano
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).