{"thread":{"id":"57382","subject":"[PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","startedAt":"2022-02-08T09:23:58Z","lastAt":"2022-02-10T17:20:11Z","messageCount":8,"participants":["Jaydeep P Das","Bagas Sanjaya","Junio C Hamano","jaydeepjd.8914@gmail.com"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"447964","messageId":"20220208092339.651761-1-jaydeepjd.8914@gmail.com","threadId":"57382","inReplyTo":null,"subject":"[PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Jaydeep P Das","fromEmail":"jaydeepjd.8914@gmail.com","sentAt":"2022-02-08T09:23:38Z","receivedAt":"2022-02-08T09:23:58Z","isPatch":true,"sender":{"key":"jaydeepjd.8914@gmail.com","avatar":"https://avatars.githubusercontent.com/u/64089730?v=4"},"body":"Fixed code as per coding style guide.\n\nSince `|` already implies that the statement is not over, therefore\nadding a `\\` in the end is not necessary.\n\n"},{"id":"447965","messageId":"20220208092339.651761-2-jaydeepjd.8914@gmail.com","threadId":"57382","inReplyTo":"20220208092339.651761-1-jaydeepjd.8914@gmail.com","subject":"[PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Jaydeep P Das","fromEmail":"jaydeepjd.8914@gmail.com","sentAt":"2022-02-08T09:23:39Z","receivedAt":"2022-02-08T09:24:21Z","isPatch":true,"sender":{"key":"jaydeepjd.8914@gmail.com","avatar":"https://avatars.githubusercontent.com/u/64089730?v=4"},"body":"From: Jaydeep Das <jaydeepjd.8914@gmail.com>\n\nThe `|` at line end already imples that the statement is not over.\nSo a `\\` after that is redundant.\n\nSigned-off-by: Jaydeep P Das <jaydeepjd.8914@gmail.com>\n---\n t/t0015-hash.sh | 6 +++---\n 1 file changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/t/t0015-hash.sh b/t/t0015-hash.sh\nindex 291e9061f3..086822fc45 100755\n--- a/t/t0015-hash.sh\n+++ b/t/t0015-hash.sh\n@@ -15,7 +15,7 @@ test_expect_success 'test basic SHA-1 hash values' '\n \tgrep c12252ceda8be8994d5fa0290a47231c1d16aae3 actual &&\n \tprintf \"abcdefghijklmnopqrstuvwxyz\" | test-tool sha1 >actual &&\n \tgrep 32d10c7b8cf96570ca04ce37f2a19d84240d3a89 actual &&\n-\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n+\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n \t\ttest-tool sha1 >actual &&\n \tgrep 34aa973cd4c4daa4f61eeb2bdbad27316534016f actual &&\n \tprintf \"blob 0\\0\" | test-tool sha1 >actual &&\n@@ -38,10 +38,10 @@ test_expect_success 'test basic SHA-256 hash values' '\n \tprintf \"abcdefghijklmnopqrstuvwxyz\" | test-tool sha256 >actual &&\n \tgrep 71c480df93d6ae2f1efad1447c66c9525e316218cf51fc8d9ed832f2daf18b73 actual &&\n \t# Try to exercise the chunking code by turning autoflush on.\n-\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n+\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n \t\ttest-tool sha256 >actual &&\n \tgrep cdc76e5c9914fb9281a1c7e284d73e67f1809a48a497200e046d39ccc7112cd0 actual &&\n-\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" | \\\n+\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" |\n \t\ttest-tool sha256 >actual &&\n \tgrep e406ba321ca712ad35a698bf0af8d61fc4dc40eca6bdcea4697962724ccbde35 actual &&\n \tprintf \"blob 0\\0\" | test-tool sha256 >actual &&\n-- \n2.35.1\n\n"},{"id":"448079","messageId":"81e8a217-356d-65cd-3a89-f20ef9c1a5d7@gmail.com","threadId":"57382","inReplyTo":"20220208092339.651761-2-jaydeepjd.8914@gmail.com","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2022-02-10T01:18:07Z","receivedAt":"2022-02-10T01:23:40Z","isPatch":true,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 08/02/22 16.23, Jaydeep P Das wrote:\n> From: Jaydeep Das <jaydeepjd.8914@gmail.com>\n> \n> The `|` at line end already imples that the statement is not over.\n> So a `\\` after that is redundant.\n> \n> Signed-off-by: Jaydeep P Das <jaydeepjd.8914@gmail.com>\n> ---\n>   t/t0015-hash.sh | 6 +++---\n>   1 file changed, 3 insertions(+), 3 deletions(-)\n> \n> diff --git a/t/t0015-hash.sh b/t/t0015-hash.sh\n> index 291e9061f3..086822fc45 100755\n> --- a/t/t0015-hash.sh\n> +++ b/t/t0015-hash.sh\n> @@ -15,7 +15,7 @@ test_expect_success 'test basic SHA-1 hash values' '\n>   \tgrep c12252ceda8be8994d5fa0290a47231c1d16aae3 actual &&\n>   \tprintf \"abcdefghijklmnopqrstuvwxyz\" | test-tool sha1 >actual &&\n>   \tgrep 32d10c7b8cf96570ca04ce37f2a19d84240d3a89 actual &&\n> -\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n> +\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n>   \t\ttest-tool sha1 >actual &&\n>   \tgrep 34aa973cd4c4daa4f61eeb2bdbad27316534016f actual &&\n>   \tprintf \"blob 0\\0\" | test-tool sha1 >actual &&\n> @@ -38,10 +38,10 @@ test_expect_success 'test basic SHA-256 hash values' '\n>   \tprintf \"abcdefghijklmnopqrstuvwxyz\" | test-tool sha256 >actual &&\n>   \tgrep 71c480df93d6ae2f1efad1447c66c9525e316218cf51fc8d9ed832f2daf18b73 actual &&\n>   \t# Try to exercise the chunking code by turning autoflush on.\n> -\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n> +\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n>   \t\ttest-tool sha256 >actual &&\n>   \tgrep cdc76e5c9914fb9281a1c7e284d73e67f1809a48a497200e046d39ccc7112cd0 actual &&\n> -\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" | \\\n> +\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" |\n>   \t\ttest-tool sha256 >actual &&\n>   \tgrep e406ba321ca712ad35a698bf0af8d61fc4dc40eca6bdcea4697962724ccbde35 actual &&\n>   \tprintf \"blob 0\\0\" | test-tool sha256 >actual &&\n\nLooks OK.\n\nReviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"},{"id":"448082","messageId":"xmqqleyjxzs4.fsf@gitster.g","threadId":"57382","inReplyTo":"81e8a217-356d-65cd-3a89-f20ef9c1a5d7@gmail.com","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-02-10T01:42:51Z","receivedAt":"2022-02-10T02:02:30Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Bagas Sanjaya <bagasdotme@gmail.com> writes:\n\n>> -\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n>> +\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n>> -\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" | \\\n>> +\tperl -e \"$| = 1; print q{aaaaaaaaaa} for 1..100000;\" |\n>> -\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" | \\\n>> +\tperl -e \"$| = 1; print q{abcdefghijklmnopqrstuvwxyz} for 1..100000;\" |\n>>   \t\ttest-tool sha256 >actual &&\n>>   \tgrep e406ba321ca712ad35a698bf0af8d61fc4dc40eca6bdcea4697962724ccbde35 actual &&\n>>   \tprintf \"blob 0\\0\" | test-tool sha256 >actual &&\n>\n> Looks OK.\n\nYeah, with \"removed\" -> \"remove\" on the title, this would look\nperfect.\n\nThanks, both.\n"},{"id":"448099","messageId":"c64e52e1-3916-dc7a-60d7-98c324814f0e@gmail.com","threadId":"57382","inReplyTo":"xmqqleyjxzs4.fsf@gitster.g","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"","fromEmail":"jaydeepjd.8914@gmail.com","sentAt":"2022-02-10T05:52:40Z","receivedAt":"2022-02-10T05:52:47Z","isPatch":true,"sender":{"key":"jaydeepjd.8914@gmail.com","avatar":"https://avatars.githubusercontent.com/u/64089730?v=4"},"body":"Thanks for the feedback.\n\nI have a few more questions regarding contributions. \n\nI have seen that some command documentations lack consistent synopsis compared to other commands.\nIs it on purpose or are improvements to those documentations welcome ?\n\nAlso, I have read some mails about \"noise\" in the mailing list. What does that mean? Does it mean \nvery small patches (like mine)? I just want to make sure so that I donot repeat any mistakes :)\n"},{"id":"448101","messageId":"xmqq4k57xlot.fsf@gitster.g","threadId":"57382","inReplyTo":"c64e52e1-3916-dc7a-60d7-98c324814f0e@gmail.com","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-02-10T06:47:14Z","receivedAt":"2022-02-10T06:47:20Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"jaydeepjd.8914@gmail.com writes:\n\n> Thanks for the feedback.\n>\n> I have a few more questions regarding contributions. \n> I have seen that some command documentations lack consistent synopsis compared to other commands.\n> Is it on purpose or are improvements to those documentations welcome ?\n\nThat's hard to answer, as what you perceive as \"lack consistent\" may\nor may not be consistent from other people's perspective, without a\nconcrete \"here is the comparison I am talking about, and this makes\nthe two comparable\" patch.\n\n> Also, I have read some mails about \"noise\" in the mailing list. What\n> does that mean? Does it mean very small patches (like mine)? I just\n> want to make sure so that I donot repeat any mistakes :)\n\n\"noise\", \"churn\", etc. are used to refer to low value changes that\nwould interfere, by touching the same area of code or documentation,\nother topics that have greater impact.  t0015 seems to be quiescent\nright now (no topic in flight fixes or modifies it), so a small-ish\nchange that does not substantially improve it would not count as\none, at least right now ;-)\n"},{"id":"448103","messageId":"bc36eab7-62ae-2e67-aa4f-cceec5c86012@gmail.com","threadId":"57382","inReplyTo":"xmqq4k57xlot.fsf@gitster.g","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"","fromEmail":"jaydeepjd.8914@gmail.com","sentAt":"2022-02-10T07:11:55Z","receivedAt":"2022-02-10T07:12:06Z","isPatch":true,"sender":{"key":"jaydeepjd.8914@gmail.com","avatar":"https://avatars.githubusercontent.com/u/64089730?v=4"},"body":"Thanks for the quick response.\n\n> > I have a few more questions regarding contributions.\n> > I have seen that some command documentations lack consistent synopsis compared to other commands.\n> > Is it on purpose or are improvements to those documentations welcome ?\n> \n> That's hard to answer, as what you perceive as \"lack consistent\" may\n> or may not be consistent from other people's perspective, without a\n> concrete \"here is the comparison I am talking about, and this makes\n> the two comparable\" patch.\n\n\nHere is an example. The synopsis of command `send-email` vs synopsis of `commit`:\n\n```\ngit send-email [<options>] <file|directory>…​\ngit send-email [<options>] <format-patch options>\ngit send-email --dump-aliases\n```\n\n```\ngit commit [-a | --interactive | --patch] [-s] [-v] [-u<mode>] [--amend]\n\t   [--dry-run] [(-c | -C | --squash) <commit> | --fixup [(amend|reword):]<commit>)]\n\t   [-F <file> | -m <msg>] [--reset-author] [--allow-empty]\n\t   [--allow-empty-message] [--no-verify] [-e] [--author=<author>]\n\t   [--date=<date>] [--cleanup=<mode>] [--[no-]status]\n\t   [-i | -o] [--pathspec-from-file=<file> [--pathspec-file-nul]]\n\t   [(--trailer <token>[(=|:)<value>])…​] [-S[<keyid>]]\n\t   [--] [<pathspec>…​]\n```\n\nThe `commit` synopsis has a more verbose overview of all the options available compared to `send-email` synopsis.\n"},{"id":"448173","messageId":"xmqq1r0awse5.fsf@gitster.g","threadId":"57382","inReplyTo":"bc36eab7-62ae-2e67-aa4f-cceec5c86012@gmail.com","subject":"Re: [PATCH] t/t0015-hash.sh: removed unnecessary '\\' at line end","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-02-10T17:20:02Z","receivedAt":"2022-02-10T17:20:11Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"jaydeepjd.8914@gmail.com writes:\n\n> Here is an example. The synopsis of command `send-email` vs synopsis of `commit`:\n>\n> ```\n> git send-email [<options>] <file|directory>…​\n> git send-email [<options>] <format-patch options>\n> git send-email --dump-aliases\n> ```\n>\n> ```\n> git commit [-a | --interactive | --patch] [-s] [-v] [-u<mode>] [--amend]\n> \t   [--dry-run] [(-c | -C | --squash) <commit> | --fixup [(amend|reword):]<commit>)]\n> \t   [-F <file> | -m <msg>] [--reset-author] [--allow-empty]\n> \t   [--allow-empty-message] [--no-verify] [-e] [--author=<author>]\n> \t   [--date=<date>] [--cleanup=<mode>] [--[no-]status]\n> \t   [-i | -o] [--pathspec-from-file=<file> [--pathspec-file-nul]]\n> \t   [(--trailer <token>[(=|:)<value>])…​] [-S[<keyid>]]\n> \t   [--] [<pathspec>…​]\n> ```\n>\n> The `commit` synopsis has a more verbose overview of all the options available compared to `send-email` synopsis.\n\nI think the former is more modern style that leaves the description\nof options to the main text.  It also allows the synopsis section to\nmake it stand out very different operating modes instead of having\nthe alternative listed with [ A | B | C ] and having the readers\nguess if all combinations of alternatives are valid (they are often\nnot).\n\nThe former style takes more thought to write well, when a command is\nmulti-purpose and has different operating modes (cf. \"git checkout\").\n\nFor \"git commit\", even though conceptually creating a totally new\ncommit and amending the current one are two quite distinct opeating\nmodes, they pretty much take the same set of options, so I suspect\nwe can do with just one\n\n\tgit commit [<options>] [--] [<pathspec>...]\n\nin the modern style, but I dunno (that is why I said \"it takes more\nthought\" and I cannot afford much time to think it through just for\nillustration purposes).\n\nThanks.\n\n"}]}