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

Re: locally storing issues/comments/projects

From
Sahil Gautam <printfdebugging@gmail.com>
Date
Jul 9, 2025, 00:21 UTC
Message-ID
<3a8590f3-ab8d-4155-b8c1-7cd34dc9db00@gmail.com>
In-Reply-To
<xmqq4ivmtlnf.fsf@gitster.g>
On 7/9/25 3:01 AM, Junio C Hamano wrote:
> It would be very nice if these hosting providers can agree to make
> project metainformations interchangeable in an open way.

it's not just about migrations, it's about a repository being self reliant in itself. think of some git hosting provider blocking my account because of some ai algorithm, think of some disaster striking some data center or some malware deleting all the data on the servers, all these are quite possible.

having git store that data means that you clone the whole thing and doesn't matter what happens to the hosting provider, if you have the repository, you have the whole thing.

Previous: Junio C HamanoNext: Eli Schwartz
Message 3 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.