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

Re: Migrate away from vger to GitHub or (on-premise) GitLab?

From
HMHans Meiser <brille1@hotmail.com>
Date
Feb 2, 2024, 10:43 UTC
Message-ID
<DB9P195MB21302F96E3E2CD404FDBF9ACE2422@DB9P195MB2130.EURP195.PROD.OUTLOOK.COM>
In-Reply-To
<ZbxI4wNTBZ48YcTi@tapette.crustytoothpaste.net>
Show 8 quoted lines
> We've discussed moving to Markdown.  Unfortunately, while Markdown is
> great for HTML, it's pretty terrible for things that are not HTML.
> Certainly there are tools that convert Markdown to other formats, but
> I'm not aware of any single tool (outside of Pandoc[0]) that does so into
> all the formats we offer, including HTML, PDF, Texinfo, and manual
> pages.  Markdown also comes in a large variety of variants and writing
> documentation to please any substantial number of tools is very
> difficult.
Actually, there a plenty of converters out there converting Markdown to anything. You many find many websites that are using these converters for providing conversion online. In case there'd be a particular target language that actually may be missing, you may want to employ a 2-step process: e.g., just convert Markdown to HTML and from there to anything else. Once established, documentation would get updated automatically with every build and always correspond to the latest version.
I've been working with many documentation teams (e.g., Microsoft, Alphabet) who are using their own Markdown compilers for adding hyperlinks, warnings etc. in their automation script converting Markdown to HTML. In all the cases I've seen it's a simple pre-compiler, replacing particular tokens with actual Markdown content before conversion.
Moreover, Markdown commonly accepts a restricted set of HTML tags, so you may even extend Markdown inline for anything fancy.
Previous: Oswald BuddenhagenNext: Hans Meiser
Message 33 of 48 in “Migrate away from vger to GitHub or (on-premise) GitLab?”
  1. Hans MeiserFeb 1, 2024
  2. Kristoffer HaugsbakkFeb 1, 2024
  3. Hans MeiserFeb 1, 2024
  4. Antonin DelpeuchFeb 1, 2024
  5. Dragan SimicFeb 1, 2024
  6. Konstantin RyabitsevFeb 1, 2024
  7. Dragan SimicFeb 1, 2024
  8. Dragan SimicFeb 1, 2024
  9. Hans MeiserFeb 1, 2024
  10. Dragan SimicFeb 1, 2024
  11. Hans MeiserFeb 1, 2024
  12. Dragan SimicFeb 1, 2024
  13. rsbecker@nexbridge.comFeb 1, 2024
  14. Dragan SimicFeb 1, 2024
  15. Hans MeiserFeb 2, 2024
  16. Hans MeiserFeb 2, 2024
  17. Dragan SimicFeb 2, 2024
  18. Muting and unmuting threads (Was: Migrate away from vger to GitHub or (on-premise) GitLab?)Dragan Simic, Feb 2, 2024
  19. Phillip WoodFeb 2, 2024
  20. Dragan SimicFeb 2, 2024
  21. Junio C HamanoFeb 2, 2024
  22. brian m. carlsonFeb 2, 2024
  23. Patrick SteinhardtFeb 2, 2024
  24. Phillip WoodFeb 2, 2024
  25. Michal SuchánekFeb 2, 2024
  26. Dragan SimicFeb 2, 2024
  27. Oswald BuddenhagenFeb 4, 2024
  28. Dragan SimicFeb 4, 2024
  29. Michal SuchánekFeb 4, 2024
  30. Dragan SimicFeb 4, 2024
  31. Michal SuchánekFeb 4, 2024
  32. Oswald BuddenhagenFeb 5, 2024
  33. Hans MeiserFeb 2, 2024
  34. Hans MeiserFeb 2, 2024
  35. Nico WilliamsFeb 1, 2024
  36. Kristoffer HaugsbakkFeb 1, 2024
  37. Sergey OrganovFeb 2, 2024
  38. rsbecker@nexbridge.comFeb 2, 2024
  39. Theodore Ts'oFeb 2, 2024
  40. Michal SuchánekFeb 2, 2024
  41. Junio C HamanoFeb 2, 2024
  42. Theodore Ts'oFeb 2, 2024
  43. Hans MeiserFeb 6, 2024
  44. Dragan SimicFeb 6, 2024
  45. Junio C HamanoFeb 2, 2024
  46. rsbecker@nexbridge.comFeb 2, 2024
  47. Junio C HamanoFeb 2, 2024
  48. rsbecker@nexbridge.comFeb 2, 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.