patchMyFirstContribution: update mailing list sub steps

From: Kyle Lippincott <spectral@google.com>

The documentation says to send an email to majordomo. Doing so gets you an auto response saying majordomo has been turned down, and to instead visit https://subspace.kernel.org/vger.kernel.org.html and use the sub/unsub links.

Update the instructions to reference the supported mechanism for subscribing to the git mailing list. Include details like these being mailto links but the subject/body aren't necessary, since it's not obvious what to put in those fields.

Signed-off-by: Kyle Lippincott <spectral@google.com>
---
    MyFirstContribution: update mailing list sub steps

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1644%2Fspectral54%2Fmy-first-contribution-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1644/spectral54/my-first-contribution-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1644

 Documentation/MyFirstContribution.txt | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

On Fri, Jan 19, 2024 at 08:59:15PM +0000, spectral via GitGitGadget wrote:

I recommend just telling people to send a message to git+subscribe@vger.kernel.org and linking to https://subspace.kernel.org/subscribing.html for more details. While "sub/unsub" links will do the job for some people, webmail users may not have things properly configured to correctly process the mailto: links.

-K

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

Yeah, good suggestion.

Kyle, thanks for noticing the majordomo deprecation.

Perhaps something like this is agreeable to everybody?

------------ >8 ----------------------- >8 ----------------------- >8 ------------
Subject: Docs: majordomo@vger.kernel.org has been decomissioned

Update the instruction for subscribing to the Git mailing list we have on a few documentation pages.

Noticed-by: Kyle Lippincott <spectral@google.com>
Helped-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/MyFirstContribution.txt | 5 +++--
 README.md                             | 4 ++--
 2 files changed, 5 insertions(+), 4 deletions(-)

On Fri, Jan 19, 2024 at 2:26 PM Junio C Hamano <gitster@pobox.com> wrote:

This version looks good, thanks for catching README.md's reference as well.

On Fri, Jan 19, 2024, at 23:26, Junio C Hamano wrote:

Just curious. What’s the difference between `Reported-by` and `Noticed-by`? `Reported-by` is documented in `SubmittingPatches` but not the other one. Is perhaps `Reported-by` specifically meant for bug reports?

Thanks

"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:

It should be reported-by as the recent trend is to dedup similar ones without much meaningful distinction and stick to those that are listed in the document. It was just me being careless and picked one that used to be relatively common without even thinking:

 $ git rev-list --since 1.year --grep=Noticed-by: --count master
 2
 $ git rev-list --since 1.year --grep=Reported-by: --count master
 54

 $ git rev-list --since 5.year --until 4.year --grep=Noticed-by: --count master
 4
 $ git rev-list --since 5.year --until 4.year --grep=Reported-by: --count master
 102

 $ git rev-list --since 10.year --until 9.year --grep=Noticed-by: --count master
 12
 $ git rev-list --since 10.year --until 9.year --grep=Reported-by: --count master
 54

There probably is a subtle difference perceived between the two by those who used noticed-by over the years and I think you guessed their intention right.