git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 1/8] MyFirstContribution: mention contrib/contacts/git-contacts

From
LALinus Arver <linusa@google.com>
Date
Apr 9, 2024, 23:42 UTC
Message-ID
<owlyfrvurtl6.fsf@fine.c.googlers.com>
In-Reply-To
<xmqq8r1m16n1.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 11 quoted lines
> Linus Arver <linusa@google.com> writes:
>
>>> +NOTE: If you're not sure who to CC, use `contrib/contacts/git-contacts` to get a
>>> +list of reviewers you should include in the CC list. In addition, you can do
>>
>> I just realized that I could also do s/should/could here, but I assume
>> you'd prefer to modify in-place instead of me rerolling for a v4 just
>> for this change. Thanks.
>
> We do not even know if there are other things people find issues
> with in this iteration, so it is a bit too early to say that.
True.

FTR I should have added "I don't want to reroll this right now so soon to correct just this error, seems a bit premature" because that's what I meant to convey.

> In a
> case like this, if you do not feel so strongly about it (which I am
> guessing from your "I could also") either way, staying mum would
> probably be the best.
Ack.
> If you feel more strongly than that, saying
> "I plan to update 'should' -> 'could' if I end up doing v4" right
> now would be fine.
In hindsight this is what I shoould have said.
Show 5 quoted lines
> Then when there are other things you'd need to
> update after waiting for others' input, you could keep that promise.
> If there are no other things you'd want to update after waiting,
> that would be the good time to say "Here is a fixup! commit; squash
> into topic X. There is no other changes".

Makes sense, thanks. I need to set up `send-email` so that I can start sending individual patches like in your hypothetical scenario (I don't know how to do that with GGG, or if it is even possible).

Show 15 quoted lines
> For now, I inserted this extra commit between [1/8] and [2/8].
> Thanks.
>
> diff --git a/Documentation/MyFirstContribution.txt b/Documentation/MyFirstContribution.txt
> index 00f4c63cb9..bb7e4174e8 100644
> --- a/Documentation/MyFirstContribution.txt
> +++ b/Documentation/MyFirstContribution.txt
> @@ -1116,8 +1116,8 @@ $ git send-email --to=target@example.com psuh/*.patch
>  NOTE: Check `git help send-email` for some other options which you may find
>  valuable, such as changing the Reply-to address or adding more CC and BCC lines.
>  
> -NOTE: If you're not sure who to CC, use `contrib/contacts/git-contacts` to get a
> -list of reviewers you should include in the CC list. In addition, you can do
> +NOTE: If you're not sure whom to CC, running `contrib/contacts/git-contacts`
> +can list potential reviewers to put on the CC list. In addition, you can do

Nice. I think you can also remove the trailing "to put on the CC list" clause because it's somewehat redundant.

Previous: Junio C HamanoNext: Linus Arver
Message 28 of 88 in “docs: recommend using contrib/contacts/git-contacts”
  1. docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 2, 2024
  2. Patrick SteinhardtApr 2, 2024
  3. Linus ArverApr 4, 2024
  4. Matthias AßhauerApr 3, 2024
  5. Junio C HamanoApr 3, 2024
  6. Linus ArverApr 4, 2024
  7. 0/8 docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 6, 2024
  8. 1/8 MyFirstContribution: mention contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 6, 2024
  9. Junio C HamanoApr 6, 2024
  10. Linus ArverApr 9, 2024
  11. Junio C HamanoApr 9, 2024
  12. 2/8 SubmittingPatches: make 'git contacts' grep-friendlyLinus Arver via GitGitGadget, Apr 6, 2024
  13. Junio C HamanoApr 6, 2024
  14. 3/8 SubmittingPatches: mention GitGitGadgetLinus Arver via GitGitGadget, Apr 6, 2024
  15. Junio C HamanoApr 6, 2024
  16. Linus ArverApr 9, 2024
  17. Junio C HamanoApr 9, 2024
  18. 4/8 SubmittingPatches: quote commandsLinus Arver via GitGitGadget, Apr 6, 2024
  19. 5/8 SubmittingPatches: discuss reviewers firstLinus Arver via GitGitGadget, Apr 6, 2024
  20. 6/8 SubmittingPatches: dedupe discussion of security patchesLinus Arver via GitGitGadget, Apr 6, 2024
  21. 7/8 SubmittingPatches: add heading for format-patch and send-emailLinus Arver via GitGitGadget, Apr 6, 2024
  22. 8/8 SubmittingPatches: demonstrate using git-contacts with git-send-emailLinus Arver via GitGitGadget, Apr 6, 2024
  23. Junio C HamanoApr 6, 2024
  24. 0/8 docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 9, 2024
  25. 1/8 MyFirstContribution: mention contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 9, 2024
  26. Linus ArverApr 9, 2024
  27. Junio C HamanoApr 9, 2024
  28. Linus ArverApr 9, 2024
  29. Linus ArverApr 11, 2024
  30. 2/8 SubmittingPatches: make 'git contacts' grep-friendlyLinus Arver via GitGitGadget, Apr 9, 2024
  31. 3/8 SubmittingPatches: mention GitGitGadgetLinus Arver via GitGitGadget, Apr 9, 2024
  32. 4/8 SubmittingPatches: quote commandsLinus Arver via GitGitGadget, Apr 9, 2024
  33. 5/8 SubmittingPatches: discuss reviewers firstLinus Arver via GitGitGadget, Apr 9, 2024
  34. Eric SunshineApr 10, 2024
  35. Junio C HamanoApr 10, 2024
  36. Linus ArverApr 10, 2024
  37. 6/8 SubmittingPatches: dedupe discussion of security patchesLinus Arver via GitGitGadget, Apr 9, 2024
  38. 7/8 SubmittingPatches: add heading for format-patch and send-emailLinus Arver via GitGitGadget, Apr 9, 2024
  39. 8/8 SubmittingPatches: demonstrate using git-contacts with git-send-emailLinus Arver via GitGitGadget, Apr 9, 2024
  40. Kipras MelnikovasApr 11, 2024
  41. Linus ArverApr 11, 2024
  42. Kipras MelnikovasApr 12, 2024
  43. 0/8 docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 11, 2024
  44. 1/8 MyFirstContribution: mention contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 11, 2024
  45. 2/8 SubmittingPatches: clarify 'git-contacts' locationLinus Arver via GitGitGadget, Apr 11, 2024
  46. Junio C HamanoApr 12, 2024
  47. Eric SunshineApr 12, 2024
  48. Junio C HamanoApr 13, 2024
  49. Linus ArverApr 16, 2024
  50. Junio C HamanoApr 16, 2024
  51. Linus ArverApr 16, 2024
  52. Junio C HamanoApr 17, 2024
  53. Junio C HamanoApr 17, 2024
  54. Eric SunshineApr 17, 2024
  55. Junio C HamanoApr 17, 2024
  56. Linus ArverApr 17, 2024
  57. Linus ArverApr 17, 2024
  58. Linus ArverApr 18, 2024
  59. 3/8 SubmittingPatches: mention GitGitGadgetLinus Arver via GitGitGadget, Apr 11, 2024
  60. 4/8 SubmittingPatches: quote commandsLinus Arver via GitGitGadget, Apr 11, 2024
  61. 5/8 SubmittingPatches: discuss reviewers firstLinus Arver via GitGitGadget, Apr 11, 2024
  62. 6/8 SubmittingPatches: dedupe discussion of security patchesLinus Arver via GitGitGadget, Apr 11, 2024
  63. 7/8 SubmittingPatches: add heading for format-patch and send-emailLinus Arver via GitGitGadget, Apr 11, 2024
  64. 8/8 SubmittingPatches: demonstrate using git-contacts with git-send-emailLinus Arver via GitGitGadget, Apr 11, 2024
  65. Junio C HamanoApr 12, 2024
  66. Linus ArverApr 16, 2024
  67. 0/8 docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 16, 2024
  68. 1/8 MyFirstContribution: mention contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 16, 2024
  69. 2/8 SubmittingPatches: clarify 'git-contacts' locationLinus Arver via GitGitGadget, Apr 16, 2024
  70. 3/8 SubmittingPatches: mention GitGitGadgetLinus Arver via GitGitGadget, Apr 16, 2024
  71. 4/8 SubmittingPatches: quote commandsLinus Arver via GitGitGadget, Apr 16, 2024
  72. 5/8 SubmittingPatches: discuss reviewers firstLinus Arver via GitGitGadget, Apr 16, 2024
  73. 6/8 SubmittingPatches: dedupe discussion of security patchesLinus Arver via GitGitGadget, Apr 16, 2024
  74. 7/8 SubmittingPatches: add heading for format-patch and send-emailLinus Arver via GitGitGadget, Apr 16, 2024
  75. 8/8 SubmittingPatches: demonstrate using git-contacts with git-send-emailLinus Arver via GitGitGadget, Apr 16, 2024
  76. 0/8 docs: recommend using contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 18, 2024
  77. 1/8 MyFirstContribution: mention contrib/contacts/git-contactsLinus Arver via GitGitGadget, Apr 18, 2024
  78. 2/8 SubmittingPatches: clarify 'git-contacts' locationLinus Arver via GitGitGadget, Apr 18, 2024
  79. 3/8 SubmittingPatches: mention GitGitGadgetLinus Arver via GitGitGadget, Apr 18, 2024
  80. 4/8 SubmittingPatches: quote commandsLinus Arver via GitGitGadget, Apr 18, 2024
  81. 5/8 SubmittingPatches: discuss reviewers firstLinus Arver via GitGitGadget, Apr 18, 2024
  82. 6/8 SubmittingPatches: dedupe discussion of security patchesLinus Arver via GitGitGadget, Apr 18, 2024
  83. 7/8 SubmittingPatches: add heading for format-patch and send-emailLinus Arver via GitGitGadget, Apr 18, 2024
  84. 8/8 SubmittingPatches: demonstrate using git-contacts with git-send-emailLinus Arver via GitGitGadget, Apr 18, 2024
  85. Junio C HamanoApr 18, 2024
  86. [RFC] git-contacts: exclude list (was: Re: [PATCH] docs: recommend using contrib/contacts/git-contacts)Matthias Aßhauer, Apr 3, 2024
  87. Junio C HamanoApr 3, 2024
  88. Matthieu MoyApr 3, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.