From: David Timber <dxdt@dev.snart.me>
To: Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Yuezhang Mo <yuezhang.mo@sony.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Host exfatprogs repo on git.kernel.org?
Date: Wed, 29 Apr 2026 09:00:20 +0900 [thread overview]
Message-ID: <c6c4e93a-83c3-4a07-ace4-6262cdc0542b@dev.snart.me> (raw)
Hello maintainers,
After the recent Github incident, it came to my attention that the
critial companion of exfat fs, exfatprogs, is only hosted on Github. I'd
like to voice my opinion that the repo also has to be hosted elsewhere,
preferably on git.kernel.org like the other fs util projects.
I don't think it really has to be git.kernel.org, as long as the main
one(Github repo) and the secondary repos are synced simultaneously.
Sorry if it's already hosted elsewhere other than Github.
Regards,
Davo
next reply other threads:[~2026-04-29 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 0:00 David Timber [this message]
2026-04-30 14:14 ` Host exfatprogs repo on git.kernel.org? Namjae Jeon
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=c6c4e93a-83c3-4a07-ace4-6262cdc0542b@dev.snart.me \
--to=dxdt@dev.snart.me \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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