From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: BUG: wipefs dry run
Date: Thu, 29 Jun 2017 12:55:51 +0200 [thread overview]
Message-ID: <20170629105551.ceuymhnzlcj2hetn@ws.net.home> (raw)
In-Reply-To: <201706151647.06899.sweet_f_a@gmx.de>
On Thu, Jun 15, 2017 at 04:47:06PM +0200, Ruediger Meier wrote:
> ### the default list shows too many newlines
libsmartcols based now (the library resolves all output issues in this
universe... problem fixed).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2017-06-29 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 9:54 BUG: wipefs dry run Ruediger Meier
2017-05-10 10:32 ` Karel Zak
2017-05-10 10:53 ` Karel Zak
2017-05-10 11:03 ` Ruediger Meier
2017-05-26 11:21 ` Karel Zak
2017-06-15 14:47 ` Ruediger Meier
2017-06-16 9:39 ` Karel Zak
2017-06-29 10:55 ` Karel Zak [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=20170629105551.ceuymhnzlcj2hetn@ws.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.