public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Andreas Tille <tille@debian.org>,
	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 07:36:05 -0700	[thread overview]
Message-ID: <20260413143605.GH1048989@frogsfrogsfrogs> (raw)
In-Reply-To: <adzGdfbByADzoXWr@nidhogg.toxiclabs.cc>

On Mon, Apr 13, 2026 at 12:37:20PM +0200, Carlos Maiolino wrote:
> Hi Andreas.
> 
> On Sun, Apr 12, 2026 at 08:38:35AM +0200, Andreas Tille wrote:
> > 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.
> 
> I'm not sure what Salsa is, nor what Vcs fields are, I'm assuming this
> is a Debian specific thing and I'm not that familiar with Debian
> ecosystem...
> 
> I'm assuming this is something debian-specific? Perhaps Nathan can chime
> in here, because this does not think something related to xfsprogs
> upstream development?!
> 
> I'm not the xfsprogs maintainer though, but this doesn't seem to be
> concerning with xfsprogs upstream development.

It is, in the sense that (at least at one time) the debian/ files in the
upstream master branch were used to generate the debian packages.
Nowadays there's a slight divergence every now and then for Debian to
integrate patch backports to old release.

--D

      reply	other threads:[~2026-04-13 14:36 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
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 [this message]

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=20260413143605.GH1048989@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=anibal@debian.org \
    --cc=cem@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nathans@debian.org \
    --cc=tille@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