From: Andreas Tille <tille@debian.org>
To: XFS Development Team <linux-xfs@vger.kernel.org>
Cc: Anibal Monsalve Salazar <anibal@debian.org>,
Nathan Scott <nathans@debian.org>
Subject: Please migrate xfsdump and xfsprogs Debian packaging to Salsa
Date: Sun, 12 Apr 2026 08:38:35 +0200 [thread overview]
Message-ID: <ads96yii8bij-UQQ@an3as.eu> (raw)
Hi XFS Development Team,
I'm currently reviewing team-maintained packages that are not exposing
Vcs fields. I assume for some efficient team work you are maintaining
xfsdump
xfsprogs
in some Git repository, but the Vcs fields are not set and I could not
find corresponding repositories on Salsa. I'm not even sure whether you
might have some team space there or whether the Debian team might
sufficiently fulfill your needs.
I'd be happy if these packages could be maintained in a publicly visible
Git repository on Salsa, with appropriate Vcs fields set.
If there are specific reasons why this is currently not the case, I
would be interested to understand them as well.
If you need any help with creating some Git repository I can happily
do so since I have developed some training in doing this.
Thanks for your work on XFS in Debian, and best regards,
Andreas.
--
https://fam-tille.de
reply other threads:[~2026-04-12 6:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ads96yii8bij-UQQ@an3as.eu \
--to=tille@debian.org \
--cc=anibal@debian.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nathans@debian.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