From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>,
"Theodore Ts'o" <tytso@mit.edu>, xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: How to package e2scrub
Date: Thu, 30 May 2019 08:28:55 -0700 [thread overview]
Message-ID: <20190530152855.GA5390@magnolia> (raw)
In-Reply-To: <20190530060426.GA30438@infradead.org>
On Wed, May 29, 2019 at 11:04:26PM -0700, Christoph Hellwig wrote:
> On Wed, May 29, 2019 at 11:21:11AM -0700, Darrick J. Wong wrote:
> > Indeed. Eric picked "xfsprogs-xfs_scrub" for Rawhide, though I find
> > that name to be very clunky and would have preferred "xfs_scrub".
>
> Why not just xfs-scrub?
Slight preference for the package sharing a name with its key
ingredient:
# xfs_scrub /home
Bad command or file name
# apt install xfs_scrub
<stuff>
# xfs_scrub /home
WARNING: ALL DATA ON NON-REMOVABLE DISK
DRIVE C: WILL BE LOST!
Proceed with Format (Y/N)?
--D
next prev parent reply other threads:[~2019-05-30 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 12:06 How to package e2scrub Lukas Czerner
2019-05-29 18:21 ` Darrick J. Wong
2019-05-29 18:34 ` Eric Sandeen
2019-05-30 6:04 ` Christoph Hellwig
2019-05-30 15:28 ` Darrick J. Wong [this message]
2019-06-03 11:19 ` Emmanuel Florac
2019-06-03 12:39 ` Lukas Czerner
2019-05-29 23:59 ` Theodore Ts'o
2019-05-30 1:54 ` Andreas Dilger
2019-05-30 9:59 ` Jan Kara
2019-05-30 13:51 ` Theodore Ts'o
2019-05-31 10:07 ` Jan Kara
2019-05-31 14:10 ` Theodore Ts'o
2019-05-31 21:43 ` Andreas Dilger
2019-06-03 9:30 ` Jan Kara
2019-05-31 15:43 ` Darrick J. Wong
2019-06-03 12:32 ` Lukas Czerner
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=20190530152855.GA5390@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).