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: Mon, 11 Sep 2023 16:02:40 -0700 [thread overview]
Message-ID: <xmqqo7i8s48f.fsf@gitster.g> (raw)
In-Reply-To: <261907dbfafc8d7b3b048854b663e82d@manjaro.org> (Dragan Simic's message of "Mon, 11 Sep 2023 20:56:43 +0200")
Dragan Simic <dsimic@manjaro.org> writes:
> On 2023-09-03 05:43, Dragan Simic wrote:
>> On 2023-09-03 00:16, Junio C Hamano wrote:
>>> 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, everything sounds great and welcoming to the new
>> contributors,
>> who of course need to be willing to put in the required amount of
>> skill and effort.
>
> I sent a patch to the git mailing list today, about five hours ago,
> but it hasn't appeared on the list yet. Could something be wrong with
> the mail server(s), as I also received no other messages from the list
> in the last six hours or so?
It is a high-volume mailing list server and occasional hiccup is
part of regular life. Waiting a bit and then poking the postmater
at vger.kernel.org may be needed from time to time, but I am seeing
your message on the archive, so it seems "waiting" has worked fine?
next prev parent reply other threads:[~2023-09-12 2:38 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
2023-09-03 3:43 ` Dragan Simic
2023-09-11 18:56 ` Dragan Simic
2023-09-11 23:02 ` Junio C Hamano [this message]
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=xmqqo7i8s48f.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 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.