From: Sahil Gautam <printfdebugging@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: locally storing issues/comments/projects
Date: Wed, 9 Jul 2025 05:51:59 +0530 [thread overview]
Message-ID: <3a8590f3-ab8d-4155-b8c1-7cd34dc9db00@gmail.com> (raw)
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.
next prev parent reply other threads:[~2025-07-09 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:52 locally storing issues/comments/projects Sahil Gautam
2025-07-08 21:31 ` Junio C Hamano
2025-07-09 0:21 ` Sahil Gautam [this message]
2025-07-09 0:41 ` Eli Schwartz
2025-07-09 1:00 ` Sahil Gautam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a8590f3-ab8d-4155-b8c1-7cd34dc9db00@gmail.com \
--to=printfdebugging@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox