linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Germann <bastiangermann@fishpost.de>
To: linux-xfs@vger.kernel.org
Cc: Bastian Germann <bastiangermann@fishpost.de>
Subject: [PATCH 3/6] debian: remove "Priority: extra"
Date: Thu, 14 Jan 2021 19:37:44 +0100	[thread overview]
Message-ID: <20210114183747.2507-4-bastiangermann@fishpost.de> (raw)
In-Reply-To: <20210114183747.2507-1-bastiangermann@fishpost.de>

Priority "extra" was replaced by "optional" which is already used by the
package in general. There is one Priority extra left, so remove it.

Signed-off-by: Bastian Germann <bastiangermann@fishpost.de>
---
 debian/control | 1 -
 1 file changed, 1 deletion(-)

diff --git a/debian/control b/debian/control
index 34dce4d5..64e01f93 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,6 @@ Description: Utilities for managing the XFS filesystem
 
 Package: xfslibs-dev
 Section: libdevel
-Priority: extra
 Depends: libc6-dev | libc-dev, uuid-dev, xfsprogs (>= 3.0.0), ${misc:Depends}
 Breaks: xfsprogs (<< 3.0.0)
 Architecture: any
-- 
2.30.0


  parent reply	other threads:[~2021-01-14 18:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 18:37 [PATCH 0/6] debian: xfsprogs package clean-up Bastian Germann
2021-01-14 18:37 ` [PATCH 1/6] debian: cryptographically verify upstream tarball Bastian Germann
2021-01-14 18:37 ` [PATCH 2/6] debian: remove dependency on essential util-linux Bastian Germann
2021-01-14 20:48   ` Darrick J. Wong
2021-01-14 18:37 ` Bastian Germann [this message]
2021-01-14 20:48   ` [PATCH 3/6] debian: remove "Priority: extra" Darrick J. Wong
2021-01-14 18:37 ` [PATCH 4/6] debian: use Package-Type over its predecessor Bastian Germann
2021-01-14 20:51   ` Darrick J. Wong
2021-01-14 18:37 ` [PATCH 5/6] debian: add missing copyright info Bastian Germann
2021-01-14 18:37 ` [PATCH 6/6] debian: new changelog entry Bastian Germann
2021-01-14 20:56   ` Darrick J. Wong
2021-01-15  3:40 ` [PATCH 0/6] debian: xfsprogs package clean-up Nathan Scott
2021-01-15  4:14   ` Darrick J. Wong
2021-01-15 18:31     ` Eric Sandeen
2021-01-15 18:35   ` Eric Sandeen
2021-01-16  9:34   ` Bastian Germann
2021-01-18  1:37     ` Nathan Scott
2021-01-16  9:23 ` [PATCH v2 " Bastian Germann
2021-01-16  9:23   ` [PATCH v2 1/6] debian: cryptographically verify upstream tarball Bastian Germann
2021-01-16  9:23   ` [PATCH v2 2/6] debian: remove dependency on essential util-linux Bastian Germann
2021-01-16  9:23   ` [PATCH v2 3/6] debian: remove "Priority: extra" Bastian Germann
2021-01-16  9:23   ` [PATCH v2 4/6] debian: use Package-Type over its predecessor Bastian Germann
2021-01-16  9:23   ` [PATCH v2 5/6] debian: add missing copyright info Bastian Germann
2021-01-16  9:23   ` [PATCH v2 6/6] debian: new changelog entry Bastian Germann
2021-01-17  1:09   ` [PATCH v2 0/6] debian: xfsprogs package clean-up Eric Sandeen
2021-01-18  1:24     ` Nathan Scott
2021-01-18 21:33   ` Eric Sandeen
2021-01-19 15:02     ` Bastian Germann
2021-01-19 17:07       ` Eric Sandeen
2021-01-19 17:16         ` Bastian Germann
2021-01-19 21:26           ` Nathan Scott
2021-01-19 21:35             ` Bastian Germann
2021-01-19 21:42             ` Darrick J. Wong
2021-01-19 22:00             ` Eric Sandeen

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=20210114183747.2507-4-bastiangermann@fishpost.de \
    --to=bastiangermann@fishpost.de \
    --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;
as well as URLs for NNTP newsgroup(s).