From: Andreas Tille <tille@debian.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: XFS Development Team <linux-xfs@vger.kernel.org>,
Anibal Monsalve Salazar <anibal@debian.org>,
Nathan Scott <nathans@debian.org>
Subject: Re: Please migrate xfsdump and xfsprogs Debian packaging to Salsa
Date: Mon, 13 Apr 2026 13:38:52 +0200 [thread overview]
Message-ID: <adzVzC0mZ8b8lUO-@an3as.eu> (raw)
In-Reply-To: <adzH8Xwc_Qz6hwgH@nidhogg.toxiclabs.cc>
Hi Carlos,
Am Mon, Apr 13, 2026 at 12:41:08PM +0200 schrieb Carlos Maiolino:
> > > I'd be happy if these packages could be maintained in a publicly visible
> > > Git repository on Salsa, with appropriate Vcs fields set.
> >
> > That's more or less a matter of setting a couple of fields in
> > debian/control, right?
> >
> > Vcs-Browser: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> > Vcs-Git: https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git -b master
>
> ohh.. debian-specific fields for which VCS it uses seems like.
Yes, Debian specific ... and https://salsa.debian.org is Gitlab instance
Debian is using for the vast majority of packages. In general there are
good reasons to do the packaging there (for instance to not disturb
upstream maintainers like you with the communication ;-) ) but there are
exceptions from this rule. I'd be happy to hear from the persons
(Anibal and Nathan are listed) who usually care for the Debian packaging
whether such an exception are these xfs related packages.
If not I'd happily lend a helping hand to migrate the Debian packaging
to Salsa.
Kind regards
Andreas.
--
https://fam-tille.de
next prev parent reply other threads:[~2026-04-13 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 6:38 Please migrate xfsdump and xfsprogs Debian packaging to Salsa Andreas Tille
2026-04-13 3:55 ` Darrick J. Wong
2026-04-13 6:09 ` Andreas Tille
2026-04-13 10:41 ` Carlos Maiolino
2026-04-13 11:38 ` Andreas Tille [this message]
2026-04-13 12:10 ` Carlos Maiolino
2026-04-13 12:56 ` Nathan Scott
2026-04-13 10:37 ` Carlos Maiolino
2026-04-13 14:36 ` Darrick J. Wong
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=adzVzC0mZ8b8lUO-@an3as.eu \
--to=tille@debian.org \
--cc=anibal@debian.org \
--cc=cem@kernel.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