public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Sahil Gautam <printfdebugging@gmail.com>
To: git@vger.kernel.org
Subject: locally storing issues/comments/projects
Date: Tue, 8 Jul 2025 16:22:23 +0530	[thread overview]
Message-ID: <3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com> (raw)

hi

i was previously on github but recently moved to gitea  as i want to be 
sure that things won't change over night because some big company thinks 
so, things like addition of an annoying chatbot button everywhere. i now 
feel that the things like issues/projects/comments should be stored in 
separate private branches in git so that one doesn't have to depend on 
the hosting service providers.

i asked it to the gitea devs 
https://github.com/go-gitea/gitea/issues/34993#issuecomment-3048363965 
and they said that most of these operations are database-based. I 
thought what if git supports it inherently, so i write this mail :)

sahil gautam


             reply	other threads:[~2025-07-08 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 10:52 Sahil Gautam [this message]
2025-07-08 21:31 ` locally storing issues/comments/projects Junio C Hamano
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=3e964e0d-bb90-4074-a9ae-a10fb02b3f50@gmail.com \
    --to=printfdebugging@gmail.com \
    --cc=git@vger.kernel.org \
    /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