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

Re: locally storing issues/comments/projects

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 8, 2025, 21:31 UTC
Message-ID
<xmqq4ivmtlnf.fsf@gitster.g>
In-Reply-To
<3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com>
Sahil Gautam <printfdebugging@gmail.com> writes:
> thought what if git supports it inherently, so i write this mail :)
As far as I know, no.

Your worry about these hosting providers taking the non-commit project metainformation, like reviews and issues, hostage to prevent their users from defecting may be real. It would be very nice if these hosting providers can agree to make project metainformations interchangeable in an open way. It would allow not just migration between hosing providers, but may even allow federated operation to be implemented. You push your work to one site, somebody on another site comment on your commits elsewhere, etc.

Previous: Sahil GautamNext: Sahil Gautam
Message 2 of 5 in “locally storing issues/comments/projects”
  1. Sahil GautamJul 8, 2025
  2. Junio C HamanoJul 8, 2025
  3. Sahil GautamJul 9, 2025
  4. Eli SchwartzJul 9, 2025
  5. Sahil GautamJul 9, 2025

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.