From: Junio C Hamano <gitster@pobox•com>
To: jaydeepjd.8914@gmail•com
Cc: Bagas Sanjaya <bagasdotme@gmail•com>, git@vger•kernel.org
Subject: Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\' at line end
Date: Wed, 09 Feb 2022 22:47:14 -0800 [thread overview]
Message-ID: <xmqq4k57xlot.fsf@gitster.g> (raw)
In-Reply-To: <c64e52e1-3916-dc7a-60d7-98c324814f0e@gmail.com> (jaydeepjd's message of "Thu, 10 Feb 2022 11:22:40 +0530")
jaydeepjd.8914@gmail•com writes:
> Thanks for the feedback.
>
> I have a few more questions regarding contributions.
> I have seen that some command documentations lack consistent synopsis compared to other commands.
> Is it on purpose or are improvements to those documentations welcome ?
That's hard to answer, as what you perceive as "lack consistent" may
or may not be consistent from other people's perspective, without a
concrete "here is the comparison I am talking about, and this makes
the two comparable" patch.
> Also, I have read some mails about "noise" in the mailing list. What
> does that mean? Does it mean very small patches (like mine)? I just
> want to make sure so that I donot repeat any mistakes :)
"noise", "churn", etc. are used to refer to low value changes that
would interfere, by touching the same area of code or documentation,
other topics that have greater impact. t0015 seems to be quiescent
right now (no topic in flight fixes or modifies it), so a small-ish
change that does not substantially improve it would not count as
one, at least right now ;-)
next prev parent reply other threads:[~2022-02-10 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 9:23 [PATCH] t/t0015-hash.sh: removed unnecessary '\' at line end Jaydeep P Das
2022-02-08 9:23 ` Jaydeep P Das
2022-02-10 1:18 ` Bagas Sanjaya
2022-02-10 1:42 ` Junio C Hamano
2022-02-10 5:52 ` jaydeepjd.8914
2022-02-10 6:47 ` Junio C Hamano [this message]
2022-02-10 7:11 ` jaydeepjd.8914
2022-02-10 17:20 ` Junio C Hamano
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=xmqq4k57xlot.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=bagasdotme@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jaydeepjd.8914@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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