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

Re: [PATCH 3/3] SubmittingPatches: remove pine-specific hints from MUA hints

From
DHDave Huseby <dwh@linuxprogrammer.org>
Date
May 13, 2021, 14:42 UTC
Message-ID
<20210513144235.GA11882@localhost>
In-Reply-To
<87mtszrrum.fsf@evledraar.gmail.com>
On 13.05.2021 09:50, Ævar Arnfjörð Bjarmason wrote:
Show 5 quoted lines
>So I do think that if we're including such a niche guide we're better
>off splitting it into another file and linking to it, same with the
>whole guide in SubmittingPatches now teaching people to manually craft a
>patch without using git-format-patch, another obscure edge case we give
>too much space / causes distraction.

I agree with you on this approach. There's one other subtle distinction that I realized last night and that is the distinction between best practices for using email for working *with* Git and using email for working *on* Git. I think Junio pointed it out in the thread on writing down the mailing list etiquette that the Git project itself has its own etiquette that is likely different than the etiquette of other projects that use Git and email. Maybe we should make that distinction clearer.

SubmittingPatches and MyFirstContribution.txt are clearly about using email and Git to work *on* Git. So is the MailingListEtiquette.txt file I'm proposing in the other thread. Some of the tips that would go into MUA-specific files would only apply to using email and Git to work *on* Git while others are likely to be about using email and Git to work *with* Git. It is subtle but important.

IMO, I think we should have a Documentation/WorkingOnGit subfolder where all of the documentation for the Git project resides just to clarify the distinction.

Show 7 quoted lines
>In this case though I think saying anything about pine crosses the line
>from niche to obscure archaeology. We're inlining a patch for abandoned
>software that has a replacement. If we're going to say anything about
>Pine in such a list I think it should be:
>
>    Pine: abandoned and has known flowed text bugs, use its successor
>    alpine or another MUA instead.
I'm good with this. I suppose the old docs are always in Git history.

Cheers! Dave

Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 16 of 28 in “SubmittingPatches: a few unrelated minor fixes”
  1. 0/3 SubmittingPatches: a few unrelated minor fixesÆvar Arnfjörð Bjarmason, May 12, 2021
  2. 1/3 SubmittingPatches: move discussion of Signed-off-by above "send"Ævar Arnfjörð Bjarmason, May 12, 2021
  3. Felipe ContrerasMay 12, 2021
  4. Ævar Arnfjörð BjarmasonJun 7, 2021
  5. Felipe ContrerasJun 7, 2021
  6. 2/3 SubmittingPatches: replace discussion of Travis with GitHub ActionsÆvar Arnfjörð Bjarmason, May 12, 2021
  7. Đoàn Trần Công DanhMay 12, 2021
  8. Junio C HamanoMay 12, 2021
  9. 3/3 SubmittingPatches: remove pine-specific hints from MUA hintsÆvar Arnfjörð Bjarmason, May 12, 2021
  10. Dave HusebyMay 12, 2021
  11. Felipe ContrerasMay 13, 2021
  12. Dave HusebyMay 13, 2021
  13. Felipe ContrerasMay 13, 2021
  14. Dave HusebyMay 17, 2021
  15. Ævar Arnfjörð BjarmasonMay 13, 2021
  16. Dave HusebyMay 13, 2021
  17. 0/3 SubmittingPatches: a few unrelated minor fixesÆvar Arnfjörð Bjarmason, Jun 7, 2021
  18. 1/3 SubmittingPatches: move discussion of Signed-off-by above "send"Ævar Arnfjörð Bjarmason, Jun 7, 2021
  19. Đoàn Trần Công DanhJun 7, 2021
  20. 2/3 SubmittingPatches: replace discussion of Travis with GitHub ActionsÆvar Arnfjörð Bjarmason, Jun 7, 2021
  21. SZEDER GáborJun 7, 2021
  22. 3/3 SubmittingPatches: remove pine-specific hints from MUA hintsÆvar Arnfjörð Bjarmason, Jun 7, 2021
  23. Johannes SchindelinJun 7, 2021
  24. Junio C HamanoJun 8, 2021
  25. 0/2 SubmittingPatches: talk about GitHub CI, not Travis + move-onlyÆvar Arnfjörð Bjarmason, Jul 22, 2021
  26. 1/2 SubmittingPatches: move discussion of Signed-off-by above "send"Ævar Arnfjörð Bjarmason, Jul 22, 2021
  27. Bagas SanjayaJul 23, 2021
  28. 2/2 SubmittingPatches: replace discussion of Travis with GitHub ActionsÆvar Arnfjörð Bjarmason, Jul 22, 2021

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.