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

Re: [PATCH v2] MyFirstContribution: add avenues for getting help

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 16, 2019, 03:05 UTC
Message-ID
<xmqqv9rk4j1y.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20191115230637.76877-1-emilyshaffer@google.com>
Emily Shaffer <emilyshaffer@google.com> writes:
> +[[getting-help]]
> +=== Getting Help
> +
> +If you get stuck, you can seek help in the following places.

Is this list meant to be an exhaustive list of authoritative sources? IOW, are we reasonably sure that some of us would be around and give useful help, and that we do not mind readers to consider these places "officially endorsed by the project"?

Or is this meant to be a list of reasonably well-known places, but may include places where the project does not want to be associated with the quality of answers given there?

I am (implicitly) assuming that it is the former, but I think it is better to clarify what this "list of places" is meant to be.

I notice that stack overflow is missing in this list. Intended? Not that I visit there at all nor I would recommend it, but I recall seeing questions asked by more than a few people after getting bad pieces of advice there.

Show 9 quoted lines
> +==== https://public-inbox.org/git[git@vger.kernel.org]
> +
> +This is the main Git project mailing list where code reviews, version
> +announcements, design discussions, and more take place. If you fail to receive
> +help via the channels above, you can ask your question here. The Git list
> +requires plain-text-only emails and prefers inline and bottom-posting when
> +replying to mail; you will be CC'd in all replies to you. Optionally, you can
> +subscribe to the list by sending an email to majordomo@vger.kernel.org with
> +"subscribe git" in the body.

Sounds good; I agree with Denton, especially with the mention of "you must join" on the other mailing list, that it is a good idea to explicitly say that subscription is optional in this entry.

You can ask questions even if you haven't tried other avenues and failed, but this entry makes it sound as if an earlier failure elsewhere is a prerequisite for asking for help here.

Thanks.
Previous: Jonathan NiederNext: Emily Shaffer
Message 7 of 44 in “MyFirstContribution: add avenues for getting help”
  1. MyFirstContribution: add avenues for getting helpEmily Shaffer, Nov 15, 2019
  2. Denton LiuNov 15, 2019
  3. Emily ShafferNov 15, 2019
  4. MyFirstContribution: add avenues for getting helpEmily Shaffer, Nov 15, 2019
  5. Johannes SchindelinNov 15, 2019
  6. Jonathan NiederNov 16, 2019
  7. Junio C HamanoNov 16, 2019
  8. Emily ShafferNov 18, 2019
  9. Junio C HamanoNov 19, 2019
  10. SZEDER GáborNov 19, 2019
  11. Johannes SchindelinNov 19, 2019
  12. SZEDER GáborNov 19, 2019
  13. Eric WongNov 20, 2019
  14. Johannes SchindelinNov 20, 2019
  15. SZEDER GáborNov 20, 2019
  16. Kerry, RichardNov 20, 2019
  17. Junio C HamanoNov 20, 2019
  18. SZEDER GáborNov 19, 2019
  19. MyFirstContribution: add avenues for getting helpEmily Shaffer, Dec 13, 2019
  20. Derrick StoleeDec 13, 2019
  21. Emily ShafferDec 13, 2019
  22. MyFirstContribution: add avenues for getting helpEmily Shaffer, Dec 13, 2019
  23. Junio C HamanoDec 13, 2019
  24. Emily ShafferDec 13, 2019
  25. Junio C HamanoDec 13, 2019
  26. MyFirstContribution: add avenues for getting helpemilyshaffer@google.com, Jan 24, 2020
  27. Junio C HamanoJan 24, 2020
  28. Emily ShafferJan 24, 2020
  29. Emily ShafferJan 24, 2020
  30. Junio C HamanoJan 24, 2020
  31. MyFirstContribution: add avenues for getting helpEmily Shaffer, Jan 24, 2020
  32. Junio C HamanoJan 24, 2020
  33. Emily ShafferJan 24, 2020
  34. MyFirstContribution: add avenues for getting helpEmily Shaffer, Jan 24, 2020
  35. SZEDER GáborJan 24, 2020
  36. Junio C HamanoJan 24, 2020
  37. SZEDER GáborFeb 6, 2020
  38. Junio C HamanoFeb 6, 2020
  39. Emily ShafferFeb 6, 2020
  40. Emily ShafferFeb 6, 2020
  41. MyFirstContribution: rephrase contact infoEmily Shaffer, Feb 14, 2020
  42. Jonathan NiederFeb 14, 2020
  43. Junio C HamanoFeb 14, 2020
  44. Junio C HamanoJan 24, 2020

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.