From: Junio C Hamano <gitster@pobox.com>
To: Sahil Gautam <printfdebugging@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: locally storing issues/comments/projects
Date: Tue, 08 Jul 2025 14:31:16 -0700 [thread overview]
Message-ID: <xmqq4ivmtlnf.fsf@gitster.g> (raw)
In-Reply-To: <3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com> (Sahil Gautam's message of "Tue, 8 Jul 2025 16:22:23 +0530")
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.
next prev parent reply other threads:[~2025-07-08 21:31 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 [this message]
2025-07-09 0:21 ` Sahil Gautam
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=xmqq4ivmtlnf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=printfdebugging@gmail.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