From: Karel Zak <kzak@redhat.com>
To: Chris Hofstaedtler <zeha@debian.org>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] hexdump: automatically use -C when called as hd
Date: Wed, 24 Jun 2020 16:41:17 +0200 [thread overview]
Message-ID: <20200624144117.k2aiarwbz6puqxkc@ws.net.home> (raw)
In-Reply-To: <20200623001430.890832-1-zeha@debian.org>
On Tue, Jun 23, 2020 at 12:14:30AM +0000, Chris Hofstaedtler wrote:
> When invoking hexdump as hd enable the "Canonical" format to by
> default, implying the -C option.
Well, I personally prefer aliases too, but ...
> This is historic behaviour on Debian and apparently also on FreeBSD.
> Some Debian users have asked for this to be restored, after Debian
> switched to util-linux' hexdump and hd.
if BSD implements it 24 years ago than it's probably good idea to
follow this manner to make util-linux more portable.
Merged to the "next" branch (it's too late for v2.36).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-06-24 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 0:14 [PATCH] hexdump: automatically use -C when called as hd Chris Hofstaedtler
2020-06-23 11:17 ` Sami Kerola
2020-06-23 17:06 ` Chris Hofstaedtler
2020-06-24 14:41 ` 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=20200624144117.k2aiarwbz6puqxkc@ws.net.home \
--to=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
--cc=zeha@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;
as well as URLs for NNTP newsgroup(s).