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
DSDragan Simic <dsimic@manjaro.org>
Date
Feb 1, 2024, 17:49 UTC
Message-ID
<c3b6de0c2ccf71f0dfa5aff06fa63d8f@manjaro.org>
In-Reply-To
<DB9P195MB21301E5E271567256303443CE2432@DB9P195MB2130.EURP195.PROD.OUTLOOK.COM>
On 2024-02-01 18:28, Hans Meiser wrote:
Show 5 quoted lines
> Thank you for enlightening me and elaborating on all of these very
> important facts!
> 
> Just to make sure: So "git" is considered part of the kernel? And the
> "git documentation" is considered part of the kernel, too?
Of course it isn't.
Show 10 quoted lines
> Shouldn't these topics be separated then into separate repositories,
> particularly the git documentation?
> 
> For people like me, who are contributing to dozens of documentations
> on GitHub (and GitLab) … We don't focus on the kernel alone. We
> receive dozens of important technical, business and financially
> important e-mails from different sources day by day. So, people like
> me need some modern, common channels/tools for contributing. (If
> contribution is considered helpful and valuable by the kernel team at
> all.)

Could you, please, clarify what kind of git documentation are you referring to? Are you having git man pages in mind?

Show 10 quoted lines
> With todays platforms, issues can be created by e-mail and e-mails
> will be received with each issue update. It's even possible to upload
> patches via REST services. No web browser required. So this would keep
> mailing list users acquainted to their habit.
> 
> Setting up a local (on-premise) GitLab or Azure DevOps server for
> long-term use should not be impossible. I'm running each of these
> myself. Once installed on-premise, the installation wouldn't be bound
> to any continuous support. All it needs is a provider for keeping the
> server machine running.

Quite frankly, I think you've missed some important points from the Konstantin's message. To sum it up a bit, not having continuous support is simply unacceptable for any kind of a long-term project.

Previous: Hans MeiserNext: Hans Meiser
Message 10 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.