{"thread":{"id":"55671","subject":"[PATCH 0/3] SubmittingPatches: a few unrelated minor fixes","startedAt":"2021-05-12T08:45:11Z","lastAt":"2021-07-23T06:36:44Z","messageCount":28,"participants":["Ævar Arnfjörð Bjarmason","Felipe Contreras","Đoàn Trần Công Danh","Junio C Hamano","Dave Huseby","SZEDER Gábor","Johannes Schindelin","Bagas Sanjaya"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"424301","messageId":"cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com","threadId":"55671","inReplyTo":null,"subject":"[PATCH 0/3] SubmittingPatches: a few unrelated minor fixes","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-05-12T08:44:59Z","receivedAt":"2021-05-12T08:45:11Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"A few minor updates to SubmittingPatches spotted while paging through\nit the other day.\n\nI remembered these when reading\nhttp://lore.kernel.org/git/20210512031821.6498-2-dwh@linuxprogrammer.org\n\nÆvar Arnfjörð Bjarmason (3):\n  SubmittingPatches: move discussion of Signed-off-by above \"send\"\n  SubmittingPatches: replace discussion of Travis with GitHub Actions\n  SubmittingPatches: remove pine-specific hints from MUA hints\n\n Documentation/SubmittingPatches | 258 ++++++++++++--------------------\n 1 file changed, 95 insertions(+), 163 deletions(-)\n\n-- \n2.31.1.909.g789bb6d90e\n\n"},{"id":"424302","messageId":"patch-1.3-d18a3caa07-20210512T084137Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com","subject":"[PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-05-12T08:45:00Z","receivedAt":"2021-05-12T08:45:12Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Move the section discussing the addition of a SOB trailer above the\nsection that discusses generating the patch itself. This makes sense\nas we don't want someone to go through the process of \"git\nformat-patch\", only to realize late that they should have used \"git\ncommit -s\" or equivalent.\n\nThis is a move-only change, no lines here are are being altered, only\nmoved around.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 160 ++++++++++++++++----------------\n 1 file changed, 80 insertions(+), 80 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 55287d72e0..2643062624 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -167,6 +167,86 @@ or, on an older version of Git without support for --pretty=reference:\n \tgit show -s --date=short --pretty='format:%h (%s, %ad)' <commit>\n ....\n \n+[[sign-off]]\n+=== Certify your work by adding your `Signed-off-by` trailer\n+\n+To improve tracking of who did what, we ask you to certify that you\n+wrote the patch or have the right to pass it on under the same license\n+as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n+accept your patches.\n+\n+If (and only if) you certify the below D-C-O:\n+\n+[[dco]]\n+.Developer's Certificate of Origin 1.1\n+____\n+By making a contribution to this project, I certify that:\n+\n+a. The contribution was created in whole or in part by me and I\n+   have the right to submit it under the open source license\n+   indicated in the file; or\n+\n+b. The contribution is based upon previous work that, to the best\n+   of my knowledge, is covered under an appropriate open source\n+   license and I have the right under that license to submit that\n+   work with modifications, whether created in whole or in part\n+   by me, under the same open source license (unless I am\n+   permitted to submit under a different license), as indicated\n+   in the file; or\n+\n+c. The contribution was provided directly to me by some other\n+   person who certified (a), (b) or (c) and I have not modified\n+   it.\n+\n+d. I understand and agree that this project and the contribution\n+   are public and that a record of the contribution (including all\n+   personal information I submit with it, including my sign-off) is\n+   maintained indefinitely and may be redistributed consistent with\n+   this project or the open source license(s) involved.\n+____\n+\n+you add a \"Signed-off-by\" trailer to your commit, that looks like\n+this:\n+\n+....\n+\tSigned-off-by: Random J Developer <random@developer.example.org>\n+....\n+\n+This line can be added by Git if you run the git-commit command with\n+the -s option.\n+\n+Notice that you can place your own `Signed-off-by` trailer when\n+forwarding somebody else's patch with the above rules for\n+D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n+place an in-body \"From: \" line at the beginning to properly attribute\n+the change to its true author (see (2) above).\n+\n+This procedure originally came from the Linux kernel project, so our\n+rule is quite similar to theirs, but what exactly it means to sign-off\n+your patch differs from project to project, so it may be different\n+from that of the project you are accustomed to.\n+\n+[[real-name]]\n+Also notice that a real name is used in the `Signed-off-by` trailer. Please\n+don't hide your real name.\n+\n+[[commit-trailers]]\n+If you like, you can put extra tags at the end:\n+\n+. `Reported-by:` is used to credit someone who found the bug that\n+  the patch attempts to fix.\n+. `Acked-by:` says that the person who is more familiar with the area\n+  the patch attempts to modify liked the patch.\n+. `Reviewed-by:`, unlike the other tags, can only be offered by the\n+  reviewer and means that she is completely satisfied that the patch\n+  is ready for application.  It is usually offered only after a\n+  detailed review.\n+. `Tested-by:` is used to indicate that the person applied the patch\n+  and found it to have the desired effect.\n+\n+You can also create your own tag or use one that's in common usage\n+such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n+\n [[git-tools]]\n === Generate your patch using Git tools out of your commits.\n \n@@ -302,86 +382,6 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and\n `Tested-by:` lines as necessary to credit people who helped your\n patch, and \"cc:\" them when sending such a final version for inclusion.\n \n-[[sign-off]]\n-=== Certify your work by adding your `Signed-off-by` trailer\n-\n-To improve tracking of who did what, we ask you to certify that you\n-wrote the patch or have the right to pass it on under the same license\n-as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n-accept your patches.\n-\n-If (and only if) you certify the below D-C-O:\n-\n-[[dco]]\n-.Developer's Certificate of Origin 1.1\n-____\n-By making a contribution to this project, I certify that:\n-\n-a. The contribution was created in whole or in part by me and I\n-   have the right to submit it under the open source license\n-   indicated in the file; or\n-\n-b. The contribution is based upon previous work that, to the best\n-   of my knowledge, is covered under an appropriate open source\n-   license and I have the right under that license to submit that\n-   work with modifications, whether created in whole or in part\n-   by me, under the same open source license (unless I am\n-   permitted to submit under a different license), as indicated\n-   in the file; or\n-\n-c. The contribution was provided directly to me by some other\n-   person who certified (a), (b) or (c) and I have not modified\n-   it.\n-\n-d. I understand and agree that this project and the contribution\n-   are public and that a record of the contribution (including all\n-   personal information I submit with it, including my sign-off) is\n-   maintained indefinitely and may be redistributed consistent with\n-   this project or the open source license(s) involved.\n-____\n-\n-you add a \"Signed-off-by\" trailer to your commit, that looks like\n-this:\n-\n-....\n-\tSigned-off-by: Random J Developer <random@developer.example.org>\n-....\n-\n-This line can be added by Git if you run the git-commit command with\n-the -s option.\n-\n-Notice that you can place your own `Signed-off-by` trailer when\n-forwarding somebody else's patch with the above rules for\n-D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n-place an in-body \"From: \" line at the beginning to properly attribute\n-the change to its true author (see (2) above).\n-\n-This procedure originally came from the Linux kernel project, so our\n-rule is quite similar to theirs, but what exactly it means to sign-off\n-your patch differs from project to project, so it may be different\n-from that of the project you are accustomed to.\n-\n-[[real-name]]\n-Also notice that a real name is used in the `Signed-off-by` trailer. Please\n-don't hide your real name.\n-\n-[[commit-trailers]]\n-If you like, you can put extra tags at the end:\n-\n-. `Reported-by:` is used to credit someone who found the bug that\n-  the patch attempts to fix.\n-. `Acked-by:` says that the person who is more familiar with the area\n-  the patch attempts to modify liked the patch.\n-. `Reviewed-by:`, unlike the other tags, can only be offered by the\n-  reviewer and means that she is completely satisfied that the patch\n-  is ready for application.  It is usually offered only after a\n-  detailed review.\n-. `Tested-by:` is used to indicate that the person applied the patch\n-  and found it to have the desired effect.\n-\n-You can also create your own tag or use one that's in common usage\n-such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n-\n == Subsystems with dedicated maintainers\n \n Some parts of the system have dedicated maintainers with their own\n-- \n2.31.1.909.g789bb6d90e\n\n"},{"id":"424303","messageId":"patch-2.3-7add00cc87-20210512T084137Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com","subject":"[PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-05-12T08:45:01Z","receivedAt":"2021-05-12T08:45:14Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Replace the discussion of Travis CI added in\n0e5d028a7a0 (Documentation: add setup instructions for Travis CI,\n2016-05-02) with something that covers the GitHub Actions added in\n889cacb6897 (ci: configure GitHub Actions for CI/PR, 2020-04-11).\n\nThe setup is trivial compared to using Travis, and it even works on\nWindows (that \"hopefully soon\" comment was probably out-of-date on\nTravis as well).\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 44 ++++++++++++---------------------\n 1 file changed, 16 insertions(+), 28 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 2643062624..2aa217da9c 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -74,10 +74,9 @@ the feature triggers the new behavior when it should, and to show the\n feature does not trigger when it shouldn't.  After any code change, make\n sure that the entire test suite passes.\n \n-If you have an account at GitHub (and you can get one for free to work\n-on open source projects), you can use their Travis CI integration to\n-test your changes on Linux, Mac (and hopefully soon Windows).  See\n-GitHub-Travis CI hints section for details.\n+If you have an account at GitHub pushing to a fork of\n+https://github.com/git/git will use their CI integration to test your\n+changes on Linux, Mac and Windows. See the GitHub CI section for details.\n \n Do not forget to update the documentation to describe the updated\n behavior and make sure that the resulting documentation set formats\n@@ -451,12 +450,12 @@ their trees themselves.\n   the status of various proposed changes.\n \n [[travis]]\n-== GitHub-Travis CI hints\n+== GitHub CI\n \n-With an account at GitHub (you can get one for free to work on open\n-source projects), you can use Travis CI to test your changes on Linux,\n-Mac (and hopefully soon Windows).  You can find a successful example\n-test build here: https://travis-ci.org/git/git/builds/120473209\n+With an account at GitHub you can use GitHub CI to test your changes\n+on Linux, Mac and Windows. See\n+https://github.com/git/git/actions/workflows/main.yml for examples of\n+recent CI runs.\n \n Follow these steps for the initial setup:\n \n@@ -464,31 +463,20 @@ Follow these steps for the initial setup:\n   You can find detailed instructions how to fork here:\n   https://help.github.com/articles/fork-a-repo/\n \n-. Open the Travis CI website: https://travis-ci.org\n-\n-. Press the \"Sign in with GitHub\" button.\n-\n-. Grant Travis CI permissions to access your GitHub account.\n-  You can find more information about the required permissions here:\n-  https://docs.travis-ci.com/user/github-oauth-scopes\n-\n-. Open your Travis CI profile page: https://travis-ci.org/profile\n-\n . Enable Travis CI builds for your Git fork.\n \n After the initial setup, Travis CI will run whenever you push new changes\n to your fork of Git on GitHub.  You can monitor the test state of all your\n-branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches\n+branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n \n If a branch did not pass all test cases then it is marked with a red\n-cross.  In that case you can click on the failing Travis CI job and\n-scroll all the way down in the log.  Find the line \"<-- Click here to see\n-detailed test output!\" and click on the triangle next to the log line\n-number to expand the detailed test output.  Here is such a failing\n-example: https://travis-ci.org/git/git/jobs/122676187\n-\n-Fix the problem and push your fix to your Git fork.  This will trigger\n-a new Travis CI build to ensure all tests pass.\n+cross. In that case you can click on the failing job and navigate to\n+\"ci/run-build-and-tests.sh\" and/or \"ci/print-test-failures.sh\". You\n+can also download \"Artifacts\" which are tarred (or zipped) archives\n+with test data relevant for debugging.\n+\n+Then fix the problem and push your fix to your Github fork. This will\n+trigger a new CI build to ensure all tests pass.\n \n [[mua]]\n == MUA specific hints\n-- \n2.31.1.909.g789bb6d90e\n\n"},{"id":"424304","messageId":"patch-3.3-9da5bc4a0c-20210512T084137Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com","subject":"[PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-05-12T08:45:02Z","receivedAt":"2021-05-12T08:45:17Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Remove the whole section about configuring pine with\nno-strip-whitespace-before-send.\n\nThere hasn't been a release of Pine since late 2005, in Alpine the\nno-strip-whitespace-before-send switch is already the default.\n\nThis documentation was initially added in 9740d289ee7 (Update\nSubmittingPatches to add MUA specific notes., 2005-08-26), at this\npoint it's safe to say that it's not useful to anyone anymore, let's\nremove it.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 56 ---------------------------------\n 1 file changed, 56 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 2aa217da9c..e616d20556 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -498,62 +498,6 @@ first patch.\\n\", if you really want to put in the patch e-mail,\n should come after the three-dash line that signals the end of the\n commit message.\n \n-\n-=== Pine\n-\n-(Johannes Schindelin)\n-\n-....\n-I don't know how many people still use pine, but for those poor\n-souls it may be good to mention that the quell-flowed-text is\n-needed for recent versions.\n-\n-... the \"no-strip-whitespace-before-send\" option, too. AFAIK it\n-was introduced in 4.60.\n-....\n-\n-(Linus Torvalds)\n-\n-....\n-And 4.58 needs at least this.\n-\n-diff-tree 8326dd8350be64ac7fc805f6563a1d61ad10d32c (from e886a61f76edf5410573e92e38ce22974f9c40f1)\n-Author: Linus Torvalds <torvalds@g5.osdl.org>\n-Date:   Mon Aug 15 17:23:51 2005 -0700\n-\n-    Fix pine whitespace-corruption bug\n-\n-    There's no excuse for unconditionally removing whitespace from\n-    the pico buffers on close.\n-\n-diff --git a/pico/pico.c b/pico/pico.c\n---- a/pico/pico.c\n-+++ b/pico/pico.c\n-@@ -219,7 +219,9 @@ PICO *pm;\n-\t    switch(pico_all_done){\t/* prepare for/handle final events */\n-\t      case COMP_EXIT :\t\t/* already confirmed */\n-\t\tpackheader();\n-+#if 0\n-\t\tstripwhitespace();\n-+#endif\n-\t\tc |= COMP_EXIT;\n-\t\tbreak;\n-....\n-\n-(Daniel Barkalow)\n-\n-....\n-> A patch to SubmittingPatches, MUA specific help section for\n-> users of Pine 4.63 would be very much appreciated.\n-\n-Ah, it looks like a recent version changed the default behavior to do the\n-right thing, and inverted the sense of the configuration option. (Either\n-that or Gentoo did it.) So you need to set the\n-\"no-strip-whitespace-before-send\" option, unless the option you have is\n-\"strip-whitespace-before-send\", in which case you should avoid checking\n-it.\n-....\n-\n === Thunderbird, KMail, GMail\n \n See the MUA-SPECIFIC HINTS section of linkgit:git-format-patch[1].\n-- \n2.31.1.909.g789bb6d90e\n\n"},{"id":"424308","messageId":"609ba00a1c03b_6e87020886@natae.notmuch","threadId":"55671","inReplyTo":"patch-1.3-d18a3caa07-20210512T084137Z-avarab@gmail.com","subject":"RE: [PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-05-12T09:29:46Z","receivedAt":"2021-05-12T09:30:00Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> +=== Certify your work by adding your `Signed-off-by` trailer\n> +\n> +To improve tracking of who did what, we ask you to certify that you\n> +wrote the patch or have the right to pass it on under the same license\n> +as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n> +accept your patches.\n\nThis may be me, but I would expect the phrase to make sense without the\ncomma:\n\n> we ask you to certify that you wrote the patch ... by \"signing off\"\n> your patch.\n\nWhatever you put inside the ... is additional information that doesn't\nnegate the origina sentence.\n\nSo:\n\n> To improve tracking of who did what, we ask you to certify that you\n> wrote the patch--or have the right to pass it on under the same\n> license as ours--by \"signing off\" your patch.\n\nCheers.\n\n-- \nFelipe Contreras"},{"id":"424321","messageId":"YJvI7hCoaIXkkDyl@danh.dev","threadId":"55671","inReplyTo":"patch-2.3-7add00cc87-20210512T084137Z-avarab@gmail.com","subject":"Re: [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-05-12T12:24:14Z","receivedAt":"2021-05-12T12:24:31Z","isPatch":true,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-05-12 10:45:01+0200, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:\n>  If a branch did not pass all test cases then it is marked with a red\n> -cross.  In that case you can click on the failing Travis CI job and\n> -scroll all the way down in the log.  Find the line \"<-- Click here to see\n> -detailed test output!\" and click on the triangle next to the log line\n> -number to expand the detailed test output.  Here is such a failing\n> -example: https://travis-ci.org/git/git/jobs/122676187\n> -\n> -Fix the problem and push your fix to your Git fork.  This will trigger\n> -a new Travis CI build to ensure all tests pass.\n> +cross. In that case you can click on the failing job and navigate to\n> +\"ci/run-build-and-tests.sh\" and/or \"ci/print-test-failures.sh\". You\n> +can also download \"Artifacts\" which are tarred (or zipped) archives\n> +with test data relevant for debugging.\n> +\n> +Then fix the problem and push your fix to your Github fork. This will\n\nNit: s/Github/GitHub/\n\nIt's the brand.\n\n-- \nDanh\n"},{"id":"424390","messageId":"xmqq4kf7fueq.fsf@gitster.g","threadId":"55671","inReplyTo":"patch-2.3-7add00cc87-20210512T084137Z-avarab@gmail.com","subject":"Re: [PATCH 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2021-05-12T22:40:13Z","receivedAt":"2021-05-12T23:28:01Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:\n\n> -If you have an account at GitHub (and you can get one for free to work\n> -on open source projects), you can use their Travis CI integration to\n> -test your changes on Linux, Mac (and hopefully soon Windows).  See\n> -GitHub-Travis CI hints section for details.\n> +If you have an account at GitHub pushing to a fork of\n> +https://github.com/git/git will use their CI integration to test your\n> +changes on Linux, Mac and Windows. See the GitHub CI section for details.\n\ns/If you have an account at GitHub pushing/Pushing/\n\nWhether pushing to a fork is possible is not even need to be said\nwith \"If you have an account\" here, as you begin the \"GitHub CI\"\nsection with \"With an account at GitHub\".\n\n    Side note: I initially started to point out the lack of comma\n    before \"pushing\", but after re-reading the paragraph, realized\n    that the part before that missing comma is better left out.\n\n> @@ -451,12 +450,12 @@ their trees themselves.\n>    the status of various proposed changes.\n>  \n>  [[travis]]\n> -== GitHub-Travis CI hints\n> +== GitHub CI\n>  \n> -With an account at GitHub (you can get one for free to work on open\n> -source projects), you can use Travis CI to test your changes on Linux,\n> -Mac (and hopefully soon Windows).  You can find a successful example\n> -test build here: https://travis-ci.org/git/git/builds/120473209\n> +With an account at GitHub you can use GitHub CI to test your changes\n\nHere, insert comma before \"you can use\".\n\n> +on Linux, Mac and Windows. See\n> +https://github.com/git/git/actions/workflows/main.yml for examples of\n> +recent CI runs.\n\nThanks.\n"},{"id":"424405","messageId":"20210512235136.GB10785@localhost","threadId":"55671","inReplyTo":"patch-3.3-9da5bc4a0c-20210512T084137Z-avarab@gmail.com","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Dave Huseby","fromEmail":"dwh@linuxprogrammer.org","sentAt":"2021-05-12T23:51:36Z","receivedAt":"2021-05-13T00:15:20Z","isPatch":true,"sender":{"key":"dwh@linuxprogrammer.org","avatar":null},"body":"On 12.05.2021 10:45, Ævar Arnfjörð Bjarmason wrote:\n>There hasn't been a release of Pine since late 2005, in Alpine the\n>no-strip-whitespace-before-send switch is already the default.\n>\n>This documentation was initially added in 9740d289ee7 (Update\n>SubmittingPatches to add MUA specific notes., 2005-08-26), at this\n>point it's safe to say that it's not useful to anyone anymore, let's\n>remove it.\n\nWhat is wrong with keeping it in there? My latest version of the\netiquette patch moves my Mutt MUA config notes to this section on MUAs.\nIt could eventually become a somewhat exhaustive reference of MUA\ntweaks. Old tools may not be popular but they sometime have niche uses\nand/or userbases. My recent switch to Mutt has been mixed at best and I\nwent back to take a look at mh/nmh to see if I liked it better and I may\ngive it a go for a while to kick the tires, likely making me the only\ndeveloper that uses nmh.\n\nKeeping these notes on old tools--at the bottom of documentation no\nless--seems to have little to no \"cruft cost\" with the potential of\nhelping somebody someday, even if nostalgia is the only reason.\n\nCheers!\nDave\n"},{"id":"424425","messageId":"609cc953e0ade_329320811@natae.notmuch","threadId":"55671","inReplyTo":"20210512235136.GB10785@localhost","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-05-13T06:38:11Z","receivedAt":"2021-05-13T06:38:45Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Dave Huseby wrote:\n> On 12.05.2021 10:45, Ævar Arnfjörð Bjarmason wrote:\n> >There hasn't been a release of Pine since late 2005, in Alpine the\n> >no-strip-whitespace-before-send switch is already the default.\n> >\n> >This documentation was initially added in 9740d289ee7 (Update\n> >SubmittingPatches to add MUA specific notes., 2005-08-26), at this\n> >point it's safe to say that it's not useful to anyone anymore, let's\n> >remove it.\n> \n> What is wrong with keeping it in there? My latest version of the\n> etiquette patch moves my Mutt MUA config notes to this section on MUAs.\n> It could eventually become a somewhat exhaustive reference of MUA\n> tweaks. Old tools may not be popular but they sometime have niche uses\n> and/or userbases. My recent switch to Mutt has been mixed at best and I\n> went back to take a look at mh/nmh to see if I liked it better and I may\n> give it a go for a while to kick the tires, likely making me the only\n> developer that uses nmh.\n\nHave you tried notmuch? There's multiple clients.\n\n-- \nFelipe Contreras"},{"id":"424441","messageId":"87mtszrrum.fsf@evledraar.gmail.com","threadId":"55671","inReplyTo":"20210512235136.GB10785@localhost","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-05-13T07:50:21Z","receivedAt":"2021-05-13T07:54:47Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Wed, May 12 2021, Dave Huseby wrote:\n\n> On 12.05.2021 10:45, Ævar Arnfjörð Bjarmason wrote:\n>>There hasn't been a release of Pine since late 2005, in Alpine the\n>>no-strip-whitespace-before-send switch is already the default.\n>>\n>>This documentation was initially added in 9740d289ee7 (Update\n>>SubmittingPatches to add MUA specific notes., 2005-08-26), at this\n>>point it's safe to say that it's not useful to anyone anymore, let's\n>>remove it.\n>\n> What is wrong with keeping it in there? My latest version of the\n> etiquette patch moves my Mutt MUA config notes to this section on MUAs.\n> It could eventually become a somewhat exhaustive reference of MUA\n> tweaks. Old tools may not be popular but they sometime have niche uses\n> and/or userbases. My recent switch to Mutt has been mixed at best and I\n> went back to take a look at mh/nmh to see if I liked it better and I may\n> give it a go for a while to kick the tires, likely making me the only\n> developer that uses nmh.\n>\n> Keeping these notes on old tools--at the bottom of documentation no\n> less--seems to have little to no \"cruft cost\" with the potential of\n> helping somebody someday, even if nostalgia is the only reason.\n\nI think there's an inherent value in keeping guides like these short and\nto the point, and only including those things relevant to most readers.\n\nSo I do think that if we're including such a niche guide we're better\noff splitting it into another file and linking to it, same with the\nwhole guide in SubmittingPatches now teaching people to manually craft a\npatch without using git-format-patch, another obscure edge case we give\ntoo much space / causes distraction.\n\nIn this case though I think saying anything about pine crosses the line\nfrom niche to obscure archaeology. We're inlining a patch for abandoned\nsoftware that has a replacement. If we're going to say anything about\nPine in such a list I think it should be:\n\n    Pine: abandoned and has known flowed text bugs, use its successor\n    alpine or another MUA instead.\n"},{"id":"424473","messageId":"20210513144235.GA11882@localhost","threadId":"55671","inReplyTo":"87mtszrrum.fsf@evledraar.gmail.com","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Dave Huseby","fromEmail":"dwh@linuxprogrammer.org","sentAt":"2021-05-13T14:42:35Z","receivedAt":"2021-05-13T14:42:55Z","isPatch":true,"sender":{"key":"dwh@linuxprogrammer.org","avatar":null},"body":"On 13.05.2021 09:50, Ævar Arnfjörð Bjarmason wrote:\n>So I do think that if we're including such a niche guide we're better\n>off splitting it into another file and linking to it, same with the\n>whole guide in SubmittingPatches now teaching people to manually craft a\n>patch without using git-format-patch, another obscure edge case we give\n>too much space / causes distraction.\n\nI agree with you on this approach. There's one other subtle distinction\nthat I realized last night and that is the distinction between best\npractices for using email for working *with* Git and using email for\nworking *on* Git. I think Junio pointed it out in the thread on writing\ndown the mailing list etiquette that the Git project itself has its own\netiquette that is likely different than the etiquette of other projects\nthat use Git and email. Maybe we should make that distinction clearer.\n\nSubmittingPatches and MyFirstContribution.txt are clearly about using\nemail and Git to work *on* Git. So is the MailingListEtiquette.txt file\nI'm proposing in the other thread. Some of the tips that would go into\nMUA-specific files would only apply to using email and Git to work *on*\nGit while others are likely to be about using email and Git to work\n*with* Git. It is subtle but important.\n\nIMO, I think we should have a Documentation/WorkingOnGit subfolder where\nall of the documentation for the Git project resides just to clarify the\ndistinction.\n\n>In this case though I think saying anything about pine crosses the line\n>from niche to obscure archaeology. We're inlining a patch for abandoned\n>software that has a replacement. If we're going to say anything about\n>Pine in such a list I think it should be:\n>\n>    Pine: abandoned and has known flowed text bugs, use its successor\n>    alpine or another MUA instead.\n\nI'm good with this. I suppose the old docs are always in Git history.\n\nCheers!\nDave\n"},{"id":"424474","messageId":"20210513144550.GB11882@localhost","threadId":"55671","inReplyTo":"609cc953e0ade_329320811@natae.notmuch","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Dave Huseby","fromEmail":"dwh@linuxprogrammer.org","sentAt":"2021-05-13T14:45:50Z","receivedAt":"2021-05-13T14:46:46Z","isPatch":true,"sender":{"key":"dwh@linuxprogrammer.org","avatar":null},"body":"On 13.05.2021 01:38, Felipe Contreras wrote:\n>Have you tried notmuch? There's multiple clients.\n\nI haven't. Is that popular for mailing list style Git work? When I was\npart of the Tor Project back in the day, a couple of the main developers\nused nmh and custom python scripts to great effect. I was always\nimpressed with the CLI-fu they had.\n\nI decided to try Mutt after decades of using Alpine and Pine before\nthat. I'm open to something that is more congruent with the way I prefer\nto work. Where do you recomment I start with notmuch? Tutorials?\nFavorite client?\n\nCheers!\nDave\n"},{"id":"424501","messageId":"609d875881c7c_80a2208e7@natae.notmuch","threadId":"55671","inReplyTo":"20210513144550.GB11882@localhost","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-05-13T20:08:56Z","receivedAt":"2021-05-13T20:09:00Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Dave Huseby wrote:\n> On 13.05.2021 01:38, Felipe Contreras wrote:\n> >Have you tried notmuch? There's multiple clients.\n> \n> I haven't. Is that popular for mailing list style Git work? When I was\n> part of the Tor Project back in the day, a couple of the main developers\n> used nmh and custom python scripts to great effect. I was always\n> impressed with the CLI-fu they had.\n\nThe notmuch cli-fu is superior to anything else, by far (IMO).\n\n> Where do you recomment I start with notmuch? Tutorials?\n\nThe getting started guide [1], of course.\n\n> Favorite client?\n\nThe one I wrote ;) notmuch-vim [2] [3]\n\nCheers.\n\n[1] https://notmuchmail.org/getting-started/\n[2] https://github.com/felipec/notmuch-vim\n[3] https://www.youtube.com/watch?v=JGD7IbZmnIs\n\n-- \nFelipe Contreras\n"},{"id":"424773","messageId":"20210517190532.GA1011@localhost","threadId":"55671","inReplyTo":"609d875881c7c_80a2208e7@natae.notmuch","subject":"Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Dave Huseby","fromEmail":"dwh@linuxprogrammer.org","sentAt":"2021-05-17T19:05:32Z","receivedAt":"2021-05-17T19:05:45Z","isPatch":true,"sender":{"key":"dwh@linuxprogrammer.org","avatar":null},"body":"On 13.05.2021 15:08, Felipe Contreras wrote:\n>Cheers.\n>\n>[1] https://notmuchmail.org/getting-started/\n>[2] https://github.com/felipec/notmuch-vim\n>[3] https://www.youtube.com/watch?v=JGD7IbZmnIs\n\nOh wow. As a fellow vim user this looks amazing. I had no idea this\nexisted. Thank you for sharing.\n\nCheers!\nDave\n"},{"id":"426566","messageId":"874kea543g.fsf@evledraar.gmail.com","threadId":"55671","inReplyTo":"609ba00a1c03b_6e87020886@natae.notmuch","subject":"Re: [PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-07T11:02:08Z","receivedAt":"2021-06-07T11:03:38Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Wed, May 12 2021, Felipe Contreras wrote:\n\n> Ævar Arnfjörð Bjarmason wrote:\n>> +=== Certify your work by adding your `Signed-off-by` trailer\n>> +\n>> +To improve tracking of who did what, we ask you to certify that you\n>> +wrote the patch or have the right to pass it on under the same license\n>> +as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n>> +accept your patches.\n>\n> This may be me, but I would expect the phrase to make sense without the\n> comma:\n>\n>> we ask you to certify that you wrote the patch ... by \"signing off\"\n>> your patch.\n>\n> Whatever you put inside the ... is additional information that doesn't\n> negate the origina sentence.\n>\n> So:\n>\n>> To improve tracking of who did what, we ask you to certify that you\n>> wrote the patch--or have the right to pass it on under the same\n>> license as ours--by \"signing off\" your patch.\n>\n> Cheers.\n\nI think these are good notes, but in this commit I'm merely moving\nexisting lines around in the file so that 2/3 and 3/3 make sense, so\nI've left any change to the existing text out of v2 of this series.\n\nI welcome an effort to improve the existing wording, but I think it's\nbetter if you submit your own patch-on-top for that, I'd rather not get\nbogged down in that any more than I already am :)\n"},{"id":"426567","messageId":"patch-1.3-9fa5437bb5-20210607T110044Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","subject":"[PATCH v2 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-07T11:03:41Z","receivedAt":"2021-06-07T11:04:50Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Move the section discussing the addition of a SOB trailer above the\nsection that discusses generating the patch itself. This makes sense\nas we don't want someone to go through the process of \"git\nformat-patch\", only to realize late that they should have used \"git\ncommit -s\" or equivalent.\n\nThis is a move-only change, no lines here are are being altered, only\nmoved around.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 160 ++++++++++++++++----------------\n 1 file changed, 80 insertions(+), 80 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 55287d72e0..2643062624 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -167,6 +167,86 @@ or, on an older version of Git without support for --pretty=reference:\n \tgit show -s --date=short --pretty='format:%h (%s, %ad)' <commit>\n ....\n \n+[[sign-off]]\n+=== Certify your work by adding your `Signed-off-by` trailer\n+\n+To improve tracking of who did what, we ask you to certify that you\n+wrote the patch or have the right to pass it on under the same license\n+as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n+accept your patches.\n+\n+If (and only if) you certify the below D-C-O:\n+\n+[[dco]]\n+.Developer's Certificate of Origin 1.1\n+____\n+By making a contribution to this project, I certify that:\n+\n+a. The contribution was created in whole or in part by me and I\n+   have the right to submit it under the open source license\n+   indicated in the file; or\n+\n+b. The contribution is based upon previous work that, to the best\n+   of my knowledge, is covered under an appropriate open source\n+   license and I have the right under that license to submit that\n+   work with modifications, whether created in whole or in part\n+   by me, under the same open source license (unless I am\n+   permitted to submit under a different license), as indicated\n+   in the file; or\n+\n+c. The contribution was provided directly to me by some other\n+   person who certified (a), (b) or (c) and I have not modified\n+   it.\n+\n+d. I understand and agree that this project and the contribution\n+   are public and that a record of the contribution (including all\n+   personal information I submit with it, including my sign-off) is\n+   maintained indefinitely and may be redistributed consistent with\n+   this project or the open source license(s) involved.\n+____\n+\n+you add a \"Signed-off-by\" trailer to your commit, that looks like\n+this:\n+\n+....\n+\tSigned-off-by: Random J Developer <random@developer.example.org>\n+....\n+\n+This line can be added by Git if you run the git-commit command with\n+the -s option.\n+\n+Notice that you can place your own `Signed-off-by` trailer when\n+forwarding somebody else's patch with the above rules for\n+D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n+place an in-body \"From: \" line at the beginning to properly attribute\n+the change to its true author (see (2) above).\n+\n+This procedure originally came from the Linux kernel project, so our\n+rule is quite similar to theirs, but what exactly it means to sign-off\n+your patch differs from project to project, so it may be different\n+from that of the project you are accustomed to.\n+\n+[[real-name]]\n+Also notice that a real name is used in the `Signed-off-by` trailer. Please\n+don't hide your real name.\n+\n+[[commit-trailers]]\n+If you like, you can put extra tags at the end:\n+\n+. `Reported-by:` is used to credit someone who found the bug that\n+  the patch attempts to fix.\n+. `Acked-by:` says that the person who is more familiar with the area\n+  the patch attempts to modify liked the patch.\n+. `Reviewed-by:`, unlike the other tags, can only be offered by the\n+  reviewer and means that she is completely satisfied that the patch\n+  is ready for application.  It is usually offered only after a\n+  detailed review.\n+. `Tested-by:` is used to indicate that the person applied the patch\n+  and found it to have the desired effect.\n+\n+You can also create your own tag or use one that's in common usage\n+such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n+\n [[git-tools]]\n === Generate your patch using Git tools out of your commits.\n \n@@ -302,86 +382,6 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and\n `Tested-by:` lines as necessary to credit people who helped your\n patch, and \"cc:\" them when sending such a final version for inclusion.\n \n-[[sign-off]]\n-=== Certify your work by adding your `Signed-off-by` trailer\n-\n-To improve tracking of who did what, we ask you to certify that you\n-wrote the patch or have the right to pass it on under the same license\n-as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n-accept your patches.\n-\n-If (and only if) you certify the below D-C-O:\n-\n-[[dco]]\n-.Developer's Certificate of Origin 1.1\n-____\n-By making a contribution to this project, I certify that:\n-\n-a. The contribution was created in whole or in part by me and I\n-   have the right to submit it under the open source license\n-   indicated in the file; or\n-\n-b. The contribution is based upon previous work that, to the best\n-   of my knowledge, is covered under an appropriate open source\n-   license and I have the right under that license to submit that\n-   work with modifications, whether created in whole or in part\n-   by me, under the same open source license (unless I am\n-   permitted to submit under a different license), as indicated\n-   in the file; or\n-\n-c. The contribution was provided directly to me by some other\n-   person who certified (a), (b) or (c) and I have not modified\n-   it.\n-\n-d. I understand and agree that this project and the contribution\n-   are public and that a record of the contribution (including all\n-   personal information I submit with it, including my sign-off) is\n-   maintained indefinitely and may be redistributed consistent with\n-   this project or the open source license(s) involved.\n-____\n-\n-you add a \"Signed-off-by\" trailer to your commit, that looks like\n-this:\n-\n-....\n-\tSigned-off-by: Random J Developer <random@developer.example.org>\n-....\n-\n-This line can be added by Git if you run the git-commit command with\n-the -s option.\n-\n-Notice that you can place your own `Signed-off-by` trailer when\n-forwarding somebody else's patch with the above rules for\n-D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n-place an in-body \"From: \" line at the beginning to properly attribute\n-the change to its true author (see (2) above).\n-\n-This procedure originally came from the Linux kernel project, so our\n-rule is quite similar to theirs, but what exactly it means to sign-off\n-your patch differs from project to project, so it may be different\n-from that of the project you are accustomed to.\n-\n-[[real-name]]\n-Also notice that a real name is used in the `Signed-off-by` trailer. Please\n-don't hide your real name.\n-\n-[[commit-trailers]]\n-If you like, you can put extra tags at the end:\n-\n-. `Reported-by:` is used to credit someone who found the bug that\n-  the patch attempts to fix.\n-. `Acked-by:` says that the person who is more familiar with the area\n-  the patch attempts to modify liked the patch.\n-. `Reviewed-by:`, unlike the other tags, can only be offered by the\n-  reviewer and means that she is completely satisfied that the patch\n-  is ready for application.  It is usually offered only after a\n-  detailed review.\n-. `Tested-by:` is used to indicate that the person applied the patch\n-  and found it to have the desired effect.\n-\n-You can also create your own tag or use one that's in common usage\n-such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n-\n == Subsystems with dedicated maintainers\n \n Some parts of the system have dedicated maintainers with their own\n-- \n2.32.0.rc3.434.gd8aed1f08a7\n\n"},{"id":"426568","messageId":"patch-2.3-7d5d2854e3-20210607T110044Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","subject":"[PATCH v2 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-07T11:03:42Z","receivedAt":"2021-06-07T11:04:51Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Replace the discussion of Travis CI added in\n0e5d028a7a0 (Documentation: add setup instructions for Travis CI,\n2016-05-02) with something that covers the GitHub Actions added in\n889cacb6897 (ci: configure GitHub Actions for CI/PR, 2020-04-11).\n\nThe setup is trivial compared to using Travis, and it even works on\nWindows (that \"hopefully soon\" comment was probably out-of-date on\nTravis as well).\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 44 ++++++++++++---------------------\n 1 file changed, 16 insertions(+), 28 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 2643062624..e372d17673 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -74,10 +74,9 @@ the feature triggers the new behavior when it should, and to show the\n feature does not trigger when it shouldn't.  After any code change, make\n sure that the entire test suite passes.\n \n-If you have an account at GitHub (and you can get one for free to work\n-on open source projects), you can use their Travis CI integration to\n-test your changes on Linux, Mac (and hopefully soon Windows).  See\n-GitHub-Travis CI hints section for details.\n+Pushing to a fork of https://github.com/git/git will use their CI\n+integration to test your changes on Linux, Mac and Windows. See the\n+GitHub CI section for details.\n \n Do not forget to update the documentation to describe the updated\n behavior and make sure that the resulting documentation set formats\n@@ -451,12 +450,12 @@ their trees themselves.\n   the status of various proposed changes.\n \n [[travis]]\n-== GitHub-Travis CI hints\n+== GitHub CI\n \n-With an account at GitHub (you can get one for free to work on open\n-source projects), you can use Travis CI to test your changes on Linux,\n-Mac (and hopefully soon Windows).  You can find a successful example\n-test build here: https://travis-ci.org/git/git/builds/120473209\n+With an account at GitHub, you can use GitHub CI to test your changes\n+on Linux, Mac and Windows. See\n+https://github.com/git/git/actions/workflows/main.yml for examples of\n+recent CI runs.\n \n Follow these steps for the initial setup:\n \n@@ -464,31 +463,20 @@ Follow these steps for the initial setup:\n   You can find detailed instructions how to fork here:\n   https://help.github.com/articles/fork-a-repo/\n \n-. Open the Travis CI website: https://travis-ci.org\n-\n-. Press the \"Sign in with GitHub\" button.\n-\n-. Grant Travis CI permissions to access your GitHub account.\n-  You can find more information about the required permissions here:\n-  https://docs.travis-ci.com/user/github-oauth-scopes\n-\n-. Open your Travis CI profile page: https://travis-ci.org/profile\n-\n . Enable Travis CI builds for your Git fork.\n \n After the initial setup, Travis CI will run whenever you push new changes\n to your fork of Git on GitHub.  You can monitor the test state of all your\n-branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches\n+branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n \n If a branch did not pass all test cases then it is marked with a red\n-cross.  In that case you can click on the failing Travis CI job and\n-scroll all the way down in the log.  Find the line \"<-- Click here to see\n-detailed test output!\" and click on the triangle next to the log line\n-number to expand the detailed test output.  Here is such a failing\n-example: https://travis-ci.org/git/git/jobs/122676187\n-\n-Fix the problem and push your fix to your Git fork.  This will trigger\n-a new Travis CI build to ensure all tests pass.\n+cross. In that case you can click on the failing job and navigate to\n+\"ci/run-build-and-tests.sh\" and/or \"ci/print-test-failures.sh\". You\n+can also download \"Artifacts\" which are tarred (or zipped) archives\n+with test data relevant for debugging.\n+\n+Then fix the problem and push your fix to your GitHub fork. This will\n+trigger a new CI build to ensure all tests pass.\n \n [[mua]]\n == MUA specific hints\n-- \n2.32.0.rc3.434.gd8aed1f08a7\n\n"},{"id":"426569","messageId":"patch-3.3-a61885a198-20210607T110044Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","subject":"[PATCH v2 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-07T11:03:43Z","receivedAt":"2021-06-07T11:04:53Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Replace the whole section about configuring pine with\nno-strip-whitespace-before-send with a note that users should use\nanother MUA instead.\n\nThere hasn't been a release of Pine since late 2005, in Alpine the\nno-strip-whitespace-before-send switch is already the default.\n\nThis documentation was initially added in 9740d289ee7 (Update\nSubmittingPatches to add MUA specific notes., 2005-08-26). At this\npoint it's safe to say that it's not useful to anyone anymore, let's\nremove it.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 54 ++-------------------------------\n 1 file changed, 2 insertions(+), 52 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex e372d17673..9c859dcfef 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -501,58 +501,8 @@ commit message.\n \n === Pine\n \n-(Johannes Schindelin)\n-\n-....\n-I don't know how many people still use pine, but for those poor\n-souls it may be good to mention that the quell-flowed-text is\n-needed for recent versions.\n-\n-... the \"no-strip-whitespace-before-send\" option, too. AFAIK it\n-was introduced in 4.60.\n-....\n-\n-(Linus Torvalds)\n-\n-....\n-And 4.58 needs at least this.\n-\n-diff-tree 8326dd8350be64ac7fc805f6563a1d61ad10d32c (from e886a61f76edf5410573e92e38ce22974f9c40f1)\n-Author: Linus Torvalds <torvalds@g5.osdl.org>\n-Date:   Mon Aug 15 17:23:51 2005 -0700\n-\n-    Fix pine whitespace-corruption bug\n-\n-    There's no excuse for unconditionally removing whitespace from\n-    the pico buffers on close.\n-\n-diff --git a/pico/pico.c b/pico/pico.c\n---- a/pico/pico.c\n-+++ b/pico/pico.c\n-@@ -219,7 +219,9 @@ PICO *pm;\n-\t    switch(pico_all_done){\t/* prepare for/handle final events */\n-\t      case COMP_EXIT :\t\t/* already confirmed */\n-\t\tpackheader();\n-+#if 0\n-\t\tstripwhitespace();\n-+#endif\n-\t\tc |= COMP_EXIT;\n-\t\tbreak;\n-....\n-\n-(Daniel Barkalow)\n-\n-....\n-> A patch to SubmittingPatches, MUA specific help section for\n-> users of Pine 4.63 would be very much appreciated.\n-\n-Ah, it looks like a recent version changed the default behavior to do the\n-right thing, and inverted the sense of the configuration option. (Either\n-that or Gentoo did it.) So you need to set the\n-\"no-strip-whitespace-before-send\" option, unless the option you have is\n-\"strip-whitespace-before-send\", in which case you should avoid checking\n-it.\n-....\n+Abandoned by its uptsream and has known flowed text bugs, use its\n+successor alpine or another MUA instead.\n \n === Thunderbird, KMail, GMail\n \n-- \n2.32.0.rc3.434.gd8aed1f08a7\n\n"},{"id":"426570","messageId":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com","subject":"[PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-06-07T11:03:40Z","receivedAt":"2021-06-07T11:05:03Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"A few minor updates to SubmittingPatches spotted while paging through\nit the other day (or other month, given the delay until v2).\n\nSee\nhttps://lore.kernel.org/git/cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com/\nfor the v1 discussion. This hopefully addresses all the outstanding\ncomments with it.\n\nÆvar Arnfjörð Bjarmason (3):\n  SubmittingPatches: move discussion of Signed-off-by above \"send\"\n  SubmittingPatches: replace discussion of Travis with GitHub Actions\n  SubmittingPatches: remove pine-specific hints from MUA hints\n\n Documentation/SubmittingPatches | 256 ++++++++++++--------------------\n 1 file changed, 97 insertions(+), 159 deletions(-)\n\nRange-diff against v1:\n1:  d18a3caa07 = 1:  9fa5437bb5 SubmittingPatches: move discussion of Signed-off-by above \"send\"\n2:  7add00cc87 ! 2:  7d5d2854e3 SubmittingPatches: replace discussion of Travis with GitHub Actions\n    @@ Documentation/SubmittingPatches: the feature triggers the new behavior when it s\n     -on open source projects), you can use their Travis CI integration to\n     -test your changes on Linux, Mac (and hopefully soon Windows).  See\n     -GitHub-Travis CI hints section for details.\n    -+If you have an account at GitHub pushing to a fork of\n    -+https://github.com/git/git will use their CI integration to test your\n    -+changes on Linux, Mac and Windows. See the GitHub CI section for details.\n    ++Pushing to a fork of https://github.com/git/git will use their CI\n    ++integration to test your changes on Linux, Mac and Windows. See the\n    ++GitHub CI section for details.\n      \n      Do not forget to update the documentation to describe the updated\n      behavior and make sure that the resulting documentation set formats\n    @@ Documentation/SubmittingPatches: their trees themselves.\n     -source projects), you can use Travis CI to test your changes on Linux,\n     -Mac (and hopefully soon Windows).  You can find a successful example\n     -test build here: https://travis-ci.org/git/git/builds/120473209\n    -+With an account at GitHub you can use GitHub CI to test your changes\n    ++With an account at GitHub, you can use GitHub CI to test your changes\n     +on Linux, Mac and Windows. See\n     +https://github.com/git/git/actions/workflows/main.yml for examples of\n     +recent CI runs.\n    @@ Documentation/SubmittingPatches: Follow these steps for the initial setup:\n     +can also download \"Artifacts\" which are tarred (or zipped) archives\n     +with test data relevant for debugging.\n     +\n    -+Then fix the problem and push your fix to your Github fork. This will\n    ++Then fix the problem and push your fix to your GitHub fork. This will\n     +trigger a new CI build to ensure all tests pass.\n      \n      [[mua]]\n3:  9da5bc4a0c ! 3:  a61885a198 SubmittingPatches: remove pine-specific hints from MUA hints\n    @@ Metadata\n      ## Commit message ##\n         SubmittingPatches: remove pine-specific hints from MUA hints\n     \n    -    Remove the whole section about configuring pine with\n    -    no-strip-whitespace-before-send.\n    +    Replace the whole section about configuring pine with\n    +    no-strip-whitespace-before-send with a note that users should use\n    +    another MUA instead.\n     \n         There hasn't been a release of Pine since late 2005, in Alpine the\n         no-strip-whitespace-before-send switch is already the default.\n     \n         This documentation was initially added in 9740d289ee7 (Update\n    -    SubmittingPatches to add MUA specific notes., 2005-08-26), at this\n    +    SubmittingPatches to add MUA specific notes., 2005-08-26). At this\n         point it's safe to say that it's not useful to anyone anymore, let's\n         remove it.\n     \n         Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n     \n      ## Documentation/SubmittingPatches ##\n    -@@ Documentation/SubmittingPatches: first patch.\\n\", if you really want to put in the patch e-mail,\n    - should come after the three-dash line that signals the end of the\n    - commit message.\n    +@@ Documentation/SubmittingPatches: commit message.\n    + \n    + === Pine\n      \n    --\n    --=== Pine\n    --\n     -(Johannes Schindelin)\n     -\n     -....\n    @@ -219,7 +219,9 @@ PICO *pm;\n     -\"strip-whitespace-before-send\", in which case you should avoid checking\n     -it.\n     -....\n    --\n    ++Abandoned by its uptsream and has known flowed text bugs, use its\n    ++successor alpine or another MUA instead.\n    + \n      === Thunderbird, KMail, GMail\n      \n    - See the MUA-SPECIFIC HINTS section of linkgit:git-format-patch[1].\n-- \n2.32.0.rc3.434.gd8aed1f08a7\n\n"},{"id":"426622","messageId":"YL5CFLhmpP40ZTYJ@danh.dev","threadId":"55671","inReplyTo":"patch-1.3-9fa5437bb5-20210607T110044Z-avarab@gmail.com","subject":"Re: [PATCH v2 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2021-06-07T15:58:12Z","receivedAt":"2021-06-07T15:59:35Z","isPatch":true,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2021-06-07 13:03:41+0200, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:\n> Move the section discussing the addition of a SOB trailer above the\n> section that discusses generating the patch itself. This makes sense\n> as we don't want someone to go through the process of \"git\n> format-patch\", only to realize late that they should have used \"git\n> commit -s\" or equivalent.\n> \n> This is a move-only change, no lines here are are being altered, only\n\nNitpick: s/are are/are/;\n\nOtherwise, the move makes sense to me.\n\n> moved around.\n> \n> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n> ---\n>  Documentation/SubmittingPatches | 160 ++++++++++++++++----------------\n>  1 file changed, 80 insertions(+), 80 deletions(-)\n> \n> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\n> index 55287d72e0..2643062624 100644\n> --- a/Documentation/SubmittingPatches\n> +++ b/Documentation/SubmittingPatches\n> @@ -167,6 +167,86 @@ or, on an older version of Git without support for --pretty=reference:\n>  \tgit show -s --date=short --pretty='format:%h (%s, %ad)' <commit>\n>  ....\n>  \n> +[[sign-off]]\n> +=== Certify your work by adding your `Signed-off-by` trailer\n> +\n> +To improve tracking of who did what, we ask you to certify that you\n> +wrote the patch or have the right to pass it on under the same license\n> +as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n> +accept your patches.\n> +\n> +If (and only if) you certify the below D-C-O:\n> +\n> +[[dco]]\n> +.Developer's Certificate of Origin 1.1\n> +____\n> +By making a contribution to this project, I certify that:\n> +\n> +a. The contribution was created in whole or in part by me and I\n> +   have the right to submit it under the open source license\n> +   indicated in the file; or\n> +\n> +b. The contribution is based upon previous work that, to the best\n> +   of my knowledge, is covered under an appropriate open source\n> +   license and I have the right under that license to submit that\n> +   work with modifications, whether created in whole or in part\n> +   by me, under the same open source license (unless I am\n> +   permitted to submit under a different license), as indicated\n> +   in the file; or\n> +\n> +c. The contribution was provided directly to me by some other\n> +   person who certified (a), (b) or (c) and I have not modified\n> +   it.\n> +\n> +d. I understand and agree that this project and the contribution\n> +   are public and that a record of the contribution (including all\n> +   personal information I submit with it, including my sign-off) is\n> +   maintained indefinitely and may be redistributed consistent with\n> +   this project or the open source license(s) involved.\n> +____\n> +\n> +you add a \"Signed-off-by\" trailer to your commit, that looks like\n> +this:\n> +\n> +....\n> +\tSigned-off-by: Random J Developer <random@developer.example.org>\n> +....\n> +\n> +This line can be added by Git if you run the git-commit command with\n> +the -s option.\n> +\n> +Notice that you can place your own `Signed-off-by` trailer when\n> +forwarding somebody else's patch with the above rules for\n> +D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n> +place an in-body \"From: \" line at the beginning to properly attribute\n> +the change to its true author (see (2) above).\n> +\n> +This procedure originally came from the Linux kernel project, so our\n> +rule is quite similar to theirs, but what exactly it means to sign-off\n> +your patch differs from project to project, so it may be different\n> +from that of the project you are accustomed to.\n> +\n> +[[real-name]]\n> +Also notice that a real name is used in the `Signed-off-by` trailer. Please\n> +don't hide your real name.\n> +\n> +[[commit-trailers]]\n> +If you like, you can put extra tags at the end:\n> +\n> +. `Reported-by:` is used to credit someone who found the bug that\n> +  the patch attempts to fix.\n> +. `Acked-by:` says that the person who is more familiar with the area\n> +  the patch attempts to modify liked the patch.\n> +. `Reviewed-by:`, unlike the other tags, can only be offered by the\n> +  reviewer and means that she is completely satisfied that the patch\n> +  is ready for application.  It is usually offered only after a\n> +  detailed review.\n> +. `Tested-by:` is used to indicate that the person applied the patch\n> +  and found it to have the desired effect.\n> +\n> +You can also create your own tag or use one that's in common usage\n> +such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n> +\n>  [[git-tools]]\n>  === Generate your patch using Git tools out of your commits.\n>  \n> @@ -302,86 +382,6 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and\n>  `Tested-by:` lines as necessary to credit people who helped your\n>  patch, and \"cc:\" them when sending such a final version for inclusion.\n>  \n> -[[sign-off]]\n> -=== Certify your work by adding your `Signed-off-by` trailer\n> -\n> -To improve tracking of who did what, we ask you to certify that you\n> -wrote the patch or have the right to pass it on under the same license\n> -as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n> -accept your patches.\n> -\n> -If (and only if) you certify the below D-C-O:\n> -\n> -[[dco]]\n> -.Developer's Certificate of Origin 1.1\n> -____\n> -By making a contribution to this project, I certify that:\n> -\n> -a. The contribution was created in whole or in part by me and I\n> -   have the right to submit it under the open source license\n> -   indicated in the file; or\n> -\n> -b. The contribution is based upon previous work that, to the best\n> -   of my knowledge, is covered under an appropriate open source\n> -   license and I have the right under that license to submit that\n> -   work with modifications, whether created in whole or in part\n> -   by me, under the same open source license (unless I am\n> -   permitted to submit under a different license), as indicated\n> -   in the file; or\n> -\n> -c. The contribution was provided directly to me by some other\n> -   person who certified (a), (b) or (c) and I have not modified\n> -   it.\n> -\n> -d. I understand and agree that this project and the contribution\n> -   are public and that a record of the contribution (including all\n> -   personal information I submit with it, including my sign-off) is\n> -   maintained indefinitely and may be redistributed consistent with\n> -   this project or the open source license(s) involved.\n> -____\n> -\n> -you add a \"Signed-off-by\" trailer to your commit, that looks like\n> -this:\n> -\n> -....\n> -\tSigned-off-by: Random J Developer <random@developer.example.org>\n> -....\n> -\n> -This line can be added by Git if you run the git-commit command with\n> -the -s option.\n> -\n> -Notice that you can place your own `Signed-off-by` trailer when\n> -forwarding somebody else's patch with the above rules for\n> -D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n> -place an in-body \"From: \" line at the beginning to properly attribute\n> -the change to its true author (see (2) above).\n> -\n> -This procedure originally came from the Linux kernel project, so our\n> -rule is quite similar to theirs, but what exactly it means to sign-off\n> -your patch differs from project to project, so it may be different\n> -from that of the project you are accustomed to.\n> -\n> -[[real-name]]\n> -Also notice that a real name is used in the `Signed-off-by` trailer. Please\n> -don't hide your real name.\n> -\n> -[[commit-trailers]]\n> -If you like, you can put extra tags at the end:\n> -\n> -. `Reported-by:` is used to credit someone who found the bug that\n> -  the patch attempts to fix.\n> -. `Acked-by:` says that the person who is more familiar with the area\n> -  the patch attempts to modify liked the patch.\n> -. `Reviewed-by:`, unlike the other tags, can only be offered by the\n> -  reviewer and means that she is completely satisfied that the patch\n> -  is ready for application.  It is usually offered only after a\n> -  detailed review.\n> -. `Tested-by:` is used to indicate that the person applied the patch\n> -  and found it to have the desired effect.\n> -\n> -You can also create your own tag or use one that's in common usage\n> -such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n> -\n>  == Subsystems with dedicated maintainers\n>  \n>  Some parts of the system have dedicated maintainers with their own\n> -- \n> 2.32.0.rc3.434.gd8aed1f08a7\n> \n\n-- \nDanh\n"},{"id":"426625","messageId":"60be465278003_39c0a2084d@natae.notmuch","threadId":"55671","inReplyTo":"874kea543g.fsf@evledraar.gmail.com","subject":"Re: [PATCH 1/3] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2021-06-07T16:16:18Z","receivedAt":"2021-06-07T16:21:39Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> On Wed, May 12 2021, Felipe Contreras wrote:\n> \n> > So:\n> >\n> >> To improve tracking of who did what, we ask you to certify that you\n> >> wrote the patch--or have the right to pass it on under the same\n> >> license as ours--by \"signing off\" your patch.\n> >\n> > Cheers.\n> \n> I think these are good notes, but in this commit I'm merely moving\n> existing lines around in the file so that 2/3 and 3/3 make sense, so\n> I've left any change to the existing text out of v2 of this series.\n> \n> I welcome an effort to improve the existing wording, but I think it's\n> better if you submit your own patch-on-top for that, I'd rather not get\n> bogged down in that any more than I already am :)\n\nAll right. Fair enough.\n\n-- \nFelipe Contreras"},{"id":"426639","messageId":"20210607172542.GA6312@szeder.dev","threadId":"55671","inReplyTo":"patch-2.3-7d5d2854e3-20210607T110044Z-avarab@gmail.com","subject":"Re: [PATCH v2 2/3] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"SZEDER Gábor","fromEmail":"szeder.dev@gmail.com","sentAt":"2021-06-07T17:25:42Z","receivedAt":"2021-06-07T17:26:50Z","isPatch":true,"sender":{"key":"szeder.dev@gmail.com","avatar":"https://avatars.githubusercontent.com/u/116324?v=4"},"body":"On Mon, Jun 07, 2021 at 01:03:42PM +0200, Ævar Arnfjörð Bjarmason wrote:\n> Replace the discussion of Travis CI added in\n> 0e5d028a7a0 (Documentation: add setup instructions for Travis CI,\n> 2016-05-02) with something that covers the GitHub Actions added in\n> 889cacb6897 (ci: configure GitHub Actions for CI/PR, 2020-04-11).\n> \n> The setup is trivial compared to using Travis, and it even works on\n> Windows (that \"hopefully soon\" comment was probably out-of-date on\n> Travis as well).\n> \n> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n> ---\n>  Documentation/SubmittingPatches | 44 ++++++++++++---------------------\n>  1 file changed, 16 insertions(+), 28 deletions(-)\n> \n> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\n> index 2643062624..e372d17673 100644\n> --- a/Documentation/SubmittingPatches\n> +++ b/Documentation/SubmittingPatches\n> @@ -74,10 +74,9 @@ the feature triggers the new behavior when it should, and to show the\n>  feature does not trigger when it shouldn't.  After any code change, make\n>  sure that the entire test suite passes.\n>  \n> -If you have an account at GitHub (and you can get one for free to work\n> -on open source projects), you can use their Travis CI integration to\n> -test your changes on Linux, Mac (and hopefully soon Windows).  See\n> -GitHub-Travis CI hints section for details.\n> +Pushing to a fork of https://github.com/git/git will use their CI\n> +integration to test your changes on Linux, Mac and Windows. See the\n> +GitHub CI section for details.\n>  \n>  Do not forget to update the documentation to describe the updated\n>  behavior and make sure that the resulting documentation set formats\n> @@ -451,12 +450,12 @@ their trees themselves.\n>    the status of various proposed changes.\n>  \n>  [[travis]]\n\nWhat about this occurence of \"travis\"?\n\n> -== GitHub-Travis CI hints\n> +== GitHub CI\n>  \n> -With an account at GitHub (you can get one for free to work on open\n> -source projects), you can use Travis CI to test your changes on Linux,\n> -Mac (and hopefully soon Windows).  You can find a successful example\n> -test build here: https://travis-ci.org/git/git/builds/120473209\n> +With an account at GitHub, you can use GitHub CI to test your changes\n> +on Linux, Mac and Windows. See\n> +https://github.com/git/git/actions/workflows/main.yml for examples of\n> +recent CI runs.\n>  \n>  Follow these steps for the initial setup:\n>  \n> @@ -464,31 +463,20 @@ Follow these steps for the initial setup:\n>    You can find detailed instructions how to fork here:\n>    https://help.github.com/articles/fork-a-repo/\n>  \n> -. Open the Travis CI website: https://travis-ci.org\n> -\n> -. Press the \"Sign in with GitHub\" button.\n> -\n> -. Grant Travis CI permissions to access your GitHub account.\n> -  You can find more information about the required permissions here:\n> -  https://docs.travis-ci.com/user/github-oauth-scopes\n> -\n> -. Open your Travis CI profile page: https://travis-ci.org/profile\n> -\n>  . Enable Travis CI builds for your Git fork.\n>  \n>  After the initial setup, Travis CI will run whenever you push new changes\n\nAnd what about these two mentions of Travis CI in the context?\n\n>  to your fork of Git on GitHub.  You can monitor the test state of all your\n> -branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches\n> +branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n"},{"id":"426666","messageId":"nycvar.QRO.7.76.6.2106072346560.55@tvgsbejvaqbjf.bet","threadId":"55671","inReplyTo":"patch-3.3-a61885a198-20210607T110044Z-avarab@gmail.com","subject":"Re: [PATCH v2 3/3] SubmittingPatches: remove pine-specific hints from MUA hints","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2021-06-07T21:49:12Z","receivedAt":"2021-06-07T21:49:22Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Ævar,\n\nOn Mon, 7 Jun 2021, Ævar Arnfjörð Bjarmason wrote:\n\n> This documentation was initially added in 9740d289ee7 (Update\n> SubmittingPatches to add MUA specific notes., 2005-08-26). At this\n> point it's safe to say that it's not useful to anyone anymore, let's\n> remove it.\n\nI am using Alpine, with a config that is based on the documentation you\nremove and that you say is safe to assume to be not useful.\n\nIf you replaced the information about Pine with information about Alpine,\nI would be in favor, though.\n\nCiao,\nJohannes\n"},{"id":"426695","messageId":"xmqqsg1tqake.fsf@gitster.g","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","subject":"Re: [PATCH v2 0/3] SubmittingPatches: a few unrelated minor fixes","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2021-06-08T03:50:25Z","receivedAt":"2021-06-08T03:51:39Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:\n\n> A few minor updates to SubmittingPatches spotted while paging through\n> it the other day (or other month, given the delay until v2).\n>\n> See\n> https://lore.kernel.org/git/cover-0.3-0000000000-20210512T084137Z-avarab@gmail.com/\n> for the v1 discussion. This hopefully addresses all the outstanding\n> comments with it.\n>\n> Ævar Arnfjörð Bjarmason (3):\n>   SubmittingPatches: move discussion of Signed-off-by above \"send\"\n>   SubmittingPatches: replace discussion of Travis with GitHub Actions\n>   SubmittingPatches: remove pine-specific hints from MUA hints\n\nWill replace but it seems 2&3/3 have a bit more work to do.\n\nThanks.\n"},{"id":"430911","messageId":"cover-0.2-0000000000-20210722T120746Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com","subject":"[PATCH v3 0/2] SubmittingPatches: talk about GitHub CI, not Travis + move-only","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-07-22T12:11:22Z","receivedAt":"2021-07-22T12:11:37Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"This is a late-re-roll of this v2:\nhttps://lore.kernel.org/git/cover-0.3-0000000000-20210607T110044Z-avarab@gmail.com/\n\nI fixed the problems Đoàn Trần Công Danh and SZEDER Gábor pointed out\nin v2.\n\nI ejected the removal of the inline patch for Pine from this\nverison. Johannes suggest another approach in\nhttps://lore.kernel.org/git/nycvar.QRO.7.76.6.2106072346560.55@tvgsbejvaqbjf.bet/\n\nI think we're spending way too much reader time on [Al]pine still, but\nI don't want to write something that's accurate advice for an E-Mail\nclient I've never used, so I'm dropping it. Perhaps someone else will\npick that cleanup up...\n\nÆvar Arnfjörð Bjarmason (2):\n  SubmittingPatches: move discussion of Signed-off-by above \"send\"\n  SubmittingPatches: replace discussion of Travis with GitHub Actions\n\n Documentation/SubmittingPatches | 207 +++++++++++++++-----------------\n 1 file changed, 96 insertions(+), 111 deletions(-)\n\nRange-diff against v2:\n1:  6e2749d307 = 1:  4283f000c5 SubmittingPatches: move discussion of Signed-off-by above \"send\"\n2:  788b198520 ! 2:  ecb9924a6a SubmittingPatches: replace discussion of Travis with GitHub Actions\n    @@ Documentation/SubmittingPatches: the feature triggers the new behavior when it s\n     -GitHub-Travis CI hints section for details.\n     +Pushing to a fork of https://github.com/git/git will use their CI\n     +integration to test your changes on Linux, Mac and Windows. See the\n    -+GitHub CI section for details.\n    ++<<GHCI,GitHub CI>> section for details.\n      \n      Do not forget to update the documentation to describe the updated\n      behavior and make sure that the resulting documentation set formats\n     @@ Documentation/SubmittingPatches: their trees themselves.\n    +   entitled \"What's cooking in git.git\" and \"What's in git.git\" giving\n        the status of various proposed changes.\n      \n    - [[travis]]\n    +-[[travis]]\n     -== GitHub-Travis CI hints\n    -+== GitHub CI\n    ++== GitHub CI[[GHCI]]]\n      \n     -With an account at GitHub (you can get one for free to work on open\n     -source projects), you can use Travis CI to test your changes on Linux,\n    @@ Documentation/SubmittingPatches: Follow these steps for the initial setup:\n     -\n     -. Open your Travis CI profile page: https://travis-ci.org/profile\n     -\n    - . Enable Travis CI builds for your Git fork.\n    - \n    - After the initial setup, Travis CI will run whenever you push new changes\n    +-. Enable Travis CI builds for your Git fork.\n    +-\n    +-After the initial setup, Travis CI will run whenever you push new changes\n    ++After the initial setup, CI will run whenever you push new changes\n      to your fork of Git on GitHub.  You can monitor the test state of all your\n     -branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches\n     +branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n3:  fecc3459f1 < -:  ---------- SubmittingPatches: remove pine-specific hints from MUA hints\n-- \n2.32.0.957.gd9e39d72fe6\n\n"},{"id":"430912","messageId":"patch-1.2-4283f000c5-20210722T120746Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.2-0000000000-20210722T120746Z-avarab@gmail.com","subject":"[PATCH v3 1/2] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-07-22T12:11:23Z","receivedAt":"2021-07-22T12:11:42Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Move the section discussing the addition of a SOB trailer above the\nsection that discusses generating the patch itself. This makes sense\nas we don't want someone to go through the process of \"git\nformat-patch\", only to realize late that they should have used \"git\ncommit -s\" or equivalent.\n\nThis is a move-only change, no lines here are being altered, only\nmoved around.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 158 ++++++++++++++++----------------\n 1 file changed, 79 insertions(+), 79 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 3e215f4d80..07e2073155 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -167,6 +167,85 @@ or, on an older version of Git without support for --pretty=reference:\n \tgit show -s --date=short --pretty='format:%h (%s, %ad)' <commit>\n ....\n \n+[[sign-off]]\n+=== Certify your work by adding your `Signed-off-by` trailer\n+\n+To improve tracking of who did what, we ask you to certify that you\n+wrote the patch or have the right to pass it on under the same license\n+as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n+accept your patches.\n+\n+If (and only if) you certify the below D-C-O:\n+\n+[[dco]]\n+.Developer's Certificate of Origin 1.1\n+____\n+By making a contribution to this project, I certify that:\n+\n+a. The contribution was created in whole or in part by me and I\n+   have the right to submit it under the open source license\n+   indicated in the file; or\n+\n+b. The contribution is based upon previous work that, to the best\n+   of my knowledge, is covered under an appropriate open source\n+   license and I have the right under that license to submit that\n+   work with modifications, whether created in whole or in part\n+   by me, under the same open source license (unless I am\n+   permitted to submit under a different license), as indicated\n+   in the file; or\n+\n+c. The contribution was provided directly to me by some other\n+   person who certified (a), (b) or (c) and I have not modified\n+   it.\n+\n+d. I understand and agree that this project and the contribution\n+   are public and that a record of the contribution (including all\n+   personal information I submit with it, including my sign-off) is\n+   maintained indefinitely and may be redistributed consistent with\n+   this project or the open source license(s) involved.\n+____\n+\n+you add a \"Signed-off-by\" trailer to your commit, that looks like\n+this:\n+\n+....\n+\tSigned-off-by: Random J Developer <random@developer.example.org>\n+....\n+\n+This line can be added by Git if you run the git-commit command with\n+the -s option.\n+\n+Notice that you can place your own `Signed-off-by` trailer when\n+forwarding somebody else's patch with the above rules for\n+D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n+place an in-body \"From: \" line at the beginning to properly attribute\n+the change to its true author (see (2) above).\n+\n+This procedure originally came from the Linux kernel project, so our\n+rule is quite similar to theirs, but what exactly it means to sign-off\n+your patch differs from project to project, so it may be different\n+from that of the project you are accustomed to.\n+\n+[[real-name]]\n+Also notice that a real name is used in the `Signed-off-by` trailer. Please\n+don't hide your real name.\n+\n+[[commit-trailers]]\n+If you like, you can put extra tags at the end:\n+\n+. `Reported-by:` is used to credit someone who found the bug that\n+  the patch attempts to fix.\n+. `Acked-by:` says that the person who is more familiar with the area\n+  the patch attempts to modify liked the patch.\n+. `Reviewed-by:`, unlike the other tags, can only be offered by the\n+  reviewers themselves when they are completely satisfied with the\n+  patch after a detailed analysis.\n+. `Tested-by:` is used to indicate that the person applied the patch\n+  and found it to have the desired effect.\n+\n+You can also create your own tag or use one that's in common usage\n+such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n+\n [[git-tools]]\n === Generate your patch using Git tools out of your commits.\n \n@@ -302,85 +381,6 @@ Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and\n `Tested-by:` lines as necessary to credit people who helped your\n patch, and \"cc:\" them when sending such a final version for inclusion.\n \n-[[sign-off]]\n-=== Certify your work by adding your `Signed-off-by` trailer\n-\n-To improve tracking of who did what, we ask you to certify that you\n-wrote the patch or have the right to pass it on under the same license\n-as ours, by \"signing off\" your patch.  Without sign-off, we cannot\n-accept your patches.\n-\n-If (and only if) you certify the below D-C-O:\n-\n-[[dco]]\n-.Developer's Certificate of Origin 1.1\n-____\n-By making a contribution to this project, I certify that:\n-\n-a. The contribution was created in whole or in part by me and I\n-   have the right to submit it under the open source license\n-   indicated in the file; or\n-\n-b. The contribution is based upon previous work that, to the best\n-   of my knowledge, is covered under an appropriate open source\n-   license and I have the right under that license to submit that\n-   work with modifications, whether created in whole or in part\n-   by me, under the same open source license (unless I am\n-   permitted to submit under a different license), as indicated\n-   in the file; or\n-\n-c. The contribution was provided directly to me by some other\n-   person who certified (a), (b) or (c) and I have not modified\n-   it.\n-\n-d. I understand and agree that this project and the contribution\n-   are public and that a record of the contribution (including all\n-   personal information I submit with it, including my sign-off) is\n-   maintained indefinitely and may be redistributed consistent with\n-   this project or the open source license(s) involved.\n-____\n-\n-you add a \"Signed-off-by\" trailer to your commit, that looks like\n-this:\n-\n-....\n-\tSigned-off-by: Random J Developer <random@developer.example.org>\n-....\n-\n-This line can be added by Git if you run the git-commit command with\n-the -s option.\n-\n-Notice that you can place your own `Signed-off-by` trailer when\n-forwarding somebody else's patch with the above rules for\n-D-C-O.  Indeed you are encouraged to do so.  Do not forget to\n-place an in-body \"From: \" line at the beginning to properly attribute\n-the change to its true author (see (2) above).\n-\n-This procedure originally came from the Linux kernel project, so our\n-rule is quite similar to theirs, but what exactly it means to sign-off\n-your patch differs from project to project, so it may be different\n-from that of the project you are accustomed to.\n-\n-[[real-name]]\n-Also notice that a real name is used in the `Signed-off-by` trailer. Please\n-don't hide your real name.\n-\n-[[commit-trailers]]\n-If you like, you can put extra tags at the end:\n-\n-. `Reported-by:` is used to credit someone who found the bug that\n-  the patch attempts to fix.\n-. `Acked-by:` says that the person who is more familiar with the area\n-  the patch attempts to modify liked the patch.\n-. `Reviewed-by:`, unlike the other tags, can only be offered by the\n-  reviewers themselves when they are completely satisfied with the\n-  patch after a detailed analysis.\n-. `Tested-by:` is used to indicate that the person applied the patch\n-  and found it to have the desired effect.\n-\n-You can also create your own tag or use one that's in common usage\n-such as \"Thanks-to:\", \"Based-on-patch-by:\", or \"Mentored-by:\".\n-\n == Subsystems with dedicated maintainers\n \n Some parts of the system have dedicated maintainers with their own\n-- \n2.32.0.957.gd9e39d72fe6\n\n"},{"id":"430913","messageId":"patch-2.2-ecb9924a6a-20210722T120746Z-avarab@gmail.com","threadId":"55671","inReplyTo":"cover-0.2-0000000000-20210722T120746Z-avarab@gmail.com","subject":"[PATCH v3 2/2] SubmittingPatches: replace discussion of Travis with GitHub Actions","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-07-22T12:11:24Z","receivedAt":"2021-07-22T12:11:44Z","isPatch":true,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"Replace the discussion of Travis CI added in\n0e5d028a7a0 (Documentation: add setup instructions for Travis CI,\n2016-05-02) with something that covers the GitHub Actions added in\n889cacb6897 (ci: configure GitHub Actions for CI/PR, 2020-04-11).\n\nThe setup is trivial compared to using Travis, and it even works on\nWindows (that \"hopefully soon\" comment was probably out-of-date on\nTravis as well).\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\n---\n Documentation/SubmittingPatches | 49 ++++++++++++---------------------\n 1 file changed, 17 insertions(+), 32 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 07e2073155..e409022d93 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -74,10 +74,9 @@ the feature triggers the new behavior when it should, and to show the\n feature does not trigger when it shouldn't.  After any code change, make\n sure that the entire test suite passes.\n \n-If you have an account at GitHub (and you can get one for free to work\n-on open source projects), you can use their Travis CI integration to\n-test your changes on Linux, Mac (and hopefully soon Windows).  See\n-GitHub-Travis CI hints section for details.\n+Pushing to a fork of https://github.com/git/git will use their CI\n+integration to test your changes on Linux, Mac and Windows. See the\n+<<GHCI,GitHub CI>> section for details.\n \n Do not forget to update the documentation to describe the updated\n behavior and make sure that the resulting documentation set formats\n@@ -449,13 +448,12 @@ their trees themselves.\n   entitled \"What's cooking in git.git\" and \"What's in git.git\" giving\n   the status of various proposed changes.\n \n-[[travis]]\n-== GitHub-Travis CI hints\n+== GitHub CI[[GHCI]]]\n \n-With an account at GitHub (you can get one for free to work on open\n-source projects), you can use Travis CI to test your changes on Linux,\n-Mac (and hopefully soon Windows).  You can find a successful example\n-test build here: https://travis-ci.org/git/git/builds/120473209\n+With an account at GitHub, you can use GitHub CI to test your changes\n+on Linux, Mac and Windows. See\n+https://github.com/git/git/actions/workflows/main.yml for examples of\n+recent CI runs.\n \n Follow these steps for the initial setup:\n \n@@ -463,31 +461,18 @@ Follow these steps for the initial setup:\n   You can find detailed instructions how to fork here:\n   https://help.github.com/articles/fork-a-repo/\n \n-. Open the Travis CI website: https://travis-ci.org\n-\n-. Press the \"Sign in with GitHub\" button.\n-\n-. Grant Travis CI permissions to access your GitHub account.\n-  You can find more information about the required permissions here:\n-  https://docs.travis-ci.com/user/github-oauth-scopes\n-\n-. Open your Travis CI profile page: https://travis-ci.org/profile\n-\n-. Enable Travis CI builds for your Git fork.\n-\n-After the initial setup, Travis CI will run whenever you push new changes\n+After the initial setup, CI will run whenever you push new changes\n to your fork of Git on GitHub.  You can monitor the test state of all your\n-branches here: https://travis-ci.org/__<Your GitHub handle>__/git/branches\n+branches here: https://github.com/<Your GitHub handle>/git/actions/workflows/main.yml\n \n If a branch did not pass all test cases then it is marked with a red\n-cross.  In that case you can click on the failing Travis CI job and\n-scroll all the way down in the log.  Find the line \"<-- Click here to see\n-detailed test output!\" and click on the triangle next to the log line\n-number to expand the detailed test output.  Here is such a failing\n-example: https://travis-ci.org/git/git/jobs/122676187\n-\n-Fix the problem and push your fix to your Git fork.  This will trigger\n-a new Travis CI build to ensure all tests pass.\n+cross. In that case you can click on the failing job and navigate to\n+\"ci/run-build-and-tests.sh\" and/or \"ci/print-test-failures.sh\". You\n+can also download \"Artifacts\" which are tarred (or zipped) archives\n+with test data relevant for debugging.\n+\n+Then fix the problem and push your fix to your GitHub fork. This will\n+trigger a new CI build to ensure all tests pass.\n \n [[mua]]\n == MUA specific hints\n-- \n2.32.0.957.gd9e39d72fe6\n\n"},{"id":"430981","messageId":"1b1c3bf1-50ab-01d1-e9ff-a18b15a682a5@gmail.com","threadId":"55671","inReplyTo":"patch-1.2-4283f000c5-20210722T120746Z-avarab@gmail.com","subject":"Re: [PATCH v3 1/2] SubmittingPatches: move discussion of Signed-off-by above \"send\"","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2021-07-23T06:36:37Z","receivedAt":"2021-07-23T06:36:44Z","isPatch":true,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 22/07/21 19.11, Ævar Arnfjörð Bjarmason wrote:\n> Move the section discussing the addition of a SOB trailer above the\n> section that discusses generating the patch itself. This makes sense\n> as we don't want someone to go through the process of \"git\n> format-patch\", only to realize late that they should have used \"git\n> commit -s\" or equivalent.\n\nDid you mean someone forget to sign-off commit?\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"}]}