summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-03-26 12:06:06 -0700
committerJunio C Hamano <gitster@pobox.com>2024-03-26 12:06:06 -0700
commit57da6293b219f26239f04f9dcf2c3d43c23202bc (patch)
tree2c5f57c3843a968fdb6eaec7f52bb3ed1252e67c
parent567bbef5cfe16f4807ddd4f61c92c355326a23ca (diff)
downloadgit-57da6293b219f26239f04f9dcf2c3d43c23202bc.tar.gz
Meta/Maintnotes: clarify "uninteresting topic"
-rw-r--r--MaintNotes4
1 files changed, 2 insertions, 2 deletions
diff --git a/MaintNotes b/MaintNotes
index 57aa6dd894..919a9dc3fb 100644
--- a/MaintNotes
+++ b/MaintNotes
@@ -34,8 +34,8 @@ and Documentation/CodingGuidelines to familiarize yourself with the
project convention.
If you sent a patch and you did not hear any response from anybody for
-several days, it could be that your patch was totally uninteresting,
-but it also is possible that it was simply lost in the noise. Please
+several days, it does not necessarily mean that your patch was totally
+uninteresting; it may merely mean that it was lost in the noise. Please
do not hesitate to send a reminder message in such a case. Messages
getting lost in the noise may be a sign that those who can evaluate
your patch don't have enough mental/time bandwidth to process them