From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] New configuration option "diff.statNameWidth"
Date: Sat, 02 Sep 2023 15:16:07 -0700 [thread overview]
Message-ID: <xmqq4jkcmdaw.fsf@gitster.g> (raw)
In-Reply-To: <72c114086590b9b15a3fdd9e0d6bd67e@manjaro.org> (Dragan Simic's message of "Sat, 02 Sep 2023 20:56:58 +0200")
Dragan Simic <dsimic@manjaro.org> writes:
> Thank you very much for your thoughts and the time required to write
> it all down. I'll do my best to make my patch(es) irresistible. :)
Heh, I have to send the same from time to time, so it didn't take
that much time. Having said all the above, once we start seeing the
actual patches and its sales pitch (aka proposed commit log
message), we do guide and help polishing the patch into a better
shape, so it will not be like the contributor has to work in the
dark without knowing what level of bar their contribution has to
pass.
Thanks.
next prev parent reply other threads:[~2023-09-02 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 18:03 [RFC] New configuration option "diff.statNameWidth" Dragan Simic
2023-09-02 18:47 ` Junio C Hamano
2023-09-02 18:56 ` Dragan Simic
2023-09-02 22:16 ` Junio C Hamano [this message]
2023-09-03 3:43 ` Dragan Simic
2023-09-11 18:56 ` Dragan Simic
2023-09-11 23:02 ` Junio C Hamano
2023-09-12 0:26 ` Dragan Simic
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=xmqq4jkcmdaw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
/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).