From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
To: XFS Development Team <linux-xfs@vger.kernel.org>,
Bastian Germann <bage@debian.org>
Subject: xfsprogs_6.13.0-2_source.changes ACCEPTED into unstable
Date: Sun, 23 Feb 2025 15:11:25 +0000 [thread overview]
Message-ID: <E1tmDdd-00Esne-3X@fasolo.debian.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Thank you for your contribution to Debian.
Accepted:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 23 Feb 2025 14:32:04 +0000
Source: xfsprogs
Architecture: source
Version: 6.13.0-2
Distribution: unstable
Urgency: medium
Maintainer: XFS Development Team <linux-xfs@vger.kernel.org>
Changed-By: Bastian Germann <bage@debian.org>
Changes:
xfsprogs (6.13.0-2) unstable; urgency=medium
.
* Patch: mkfs: Correct filesize declaration
Checksums-Sha1:
92eb36614ab4bd378f1ed33b55f2beea946b20ff 2048 xfsprogs_6.13.0-2.dsc
d08caf1c5d09080e9ca978b1ee9e99900c3ebe61 13996 xfsprogs_6.13.0-2.debian.tar.xz
2bfc66d50ded3724dd493053b1502f5887a3f908 6059 xfsprogs_6.13.0-2_source.buildinfo
Checksums-Sha256:
cbd59967d673d5ee50f77b72d998a46dd2888710471a1fc824da32fc836ee61b 2048 xfsprogs_6.13.0-2.dsc
36a6e2cd26939cd22ae584b440ced0cdffdcea6851f121cb0d5204800671f97c 13996 xfsprogs_6.13.0-2.debian.tar.xz
95c5f423913d96f179cd58abd40146faf65da26bee2dd5b52c124827aa849b43 6059 xfsprogs_6.13.0-2_source.buildinfo
Files:
0928d3a2db5da22c95ac0d5c6cc01eec 2048 admin optional xfsprogs_6.13.0-2.dsc
f7b30c69faf4279b0c7a3be2222a6add 13996 admin optional xfsprogs_6.13.0-2.debian.tar.xz
94f2b1d6a43e2bfb9e615c43c62f8739 6059 admin optional xfsprogs_6.13.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAme7NB8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKDtDADSgOKRjpCrDkFsaquI4zzFVD5j9Z23yMxr
kbayVUzM2BVkKZ33ehB5uweiqniTSwjjEhdors5MabsxVJd2SDaNQ+xEanJxaRSu
9UDGgl1KfwJqpSGY6yC5SY4utzVXKXAvHzv+REh2kak51TYaDYW+gbhYkjhBUs10
dtmEPX4yaQCMIRd0XVPf/LkfSYvHwP9BnPsIGvZi3jzjbAJpQOYBqnXB+giDJ2xz
42PgmtjDMuFVQA1UyjhWfUoS+d4sYAtakAGa5FEVI+4jjGMImecf9eNaGq/dhQeA
n7s2EuY0tmGAwy4LtE+3V77zV5B0uf86W7mp5e6MPQ+AGKJ8V5qXYiP5Jhg7Op24
583qnNsafi8kUG7ZbH+vHBAKnB52CB+oggUD5xeW9D+yZdhF7rVw/Rb/182xI5uu
ulzkau+kr+rCCLXhyFuCuLk2cuFXZJxz6Y/iqVhB23UvaBmup69xXWLunFmu1i1C
1pcw6g/f0BeziJ5cBFzQLprda12hqtE=
=C9Bv
-----END PGP SIGNATURE-----
[-- Attachment #2: Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2025-02-23 15:11 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=E1tmDdd-00Esne-3X@fasolo.debian.org \
--to=ftpmaster@ftp-master.debian.org \
--cc=bage@debian.org \
--cc=linux-xfs@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