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

Re: git client enhancement request

From
Junio C Hamano <gitster@pobox.com>
Date
May 13, 2024, 18:51 UTC
Message-ID
<xmqq8r0dfsvd.fsf@gitster.g>
In-Reply-To
<m0pltptx3h.fsf@epic96565.epic.com>
Sean Allred <allred.sean@gmail.com> writes:
> Is this even technically feasible? My understanding is that
> storage implementations of each forge vary *wildly*. I don't believe
> this would be under Git's ability to implement as a project.

Not just "storage implementation", but some things are totally kept outside the control of Git proper, including user and repository management. Creating, deleting, and modifying authentication and authorization details of these things are outside the scope of Git, and forges build on their competing designs.

Previous: lbdyck@gmail.comNext: lbdyck@gmail.com
Message 4 of 8 in “git client enhancement request”
  1. lbdyck@gmail.comMay 13, 2024
  2. Sean AllredMay 13, 2024
  3. lbdyck@gmail.comMay 13, 2024
  4. Junio C HamanoMay 13, 2024
  5. lbdyck@gmail.comMay 13, 2024
  6. brian m. carlsonMay 13, 2024
  7. rsbecker@nexbridge.comMay 13, 2024
  8. lbdyck@gmail.comMay 13, 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.