From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.32
Date: Thu, 22 Mar 2018 11:24:55 +0100 [thread overview]
Message-ID: <20180322102455.wqowcj4iphqstgya@ws.net.home> (raw)
In-Reply-To: <201803221047.14002.sweet_f_a@gmx.de>
On Thu, Mar 22, 2018 at 10:47:13AM +0100, Ruediger Meier wrote:
> FYI regarding "Release Notes". I guess it's always a pain to write
yes ;-)
> that and to remember all relevant new features and options. ;)
> Just to remind you, we have have a nice tool on board which may be
> helpful.
>
> $ CU_DUMP=1 make checkusage
> $ mv /tmp/checkusage--help /tmp/checkusage--help-2.32
>
> ## ... and diff all changed --help output too see what may be
> ## worth to mention, for example:
> $ diff -uw /tmp/checkusage--help-2.31.2 /tmp/checkusage--help-2.32
Cool. Added to my release check list. Thanks.
And thanks for contribution to util-linux!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2018-03-22 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 14:53 [ANNOUNCE] util-linux v2.32 Karel Zak
2018-03-22 9:47 ` Ruediger Meier
2018-03-22 10:24 ` Karel Zak [this message]
2018-03-22 11:20 ` Ruediger Meier
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=20180322102455.wqowcj4iphqstgya@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 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).