Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.32
Date: Thu, 22 Mar 2018 12:20:27 +0100	[thread overview]
Message-ID: <201803221220.27851.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20180322102455.wqowcj4iphqstgya@ws.net.home>

On Thursday 22 March 2018 at 11:24, you wrote:
> On Thu, Mar 22, 2018 at 10:47:13AM +0100, Ruediger Meier wrote:
> > $ diff -uw  /tmp/checkusage--help-2.31.2 /tmp/checkusage--help-2.32
>
> Cool. Added to my release check list. Thanks.

Just noticed another nice diff option to see quickly which command a
change belongs too.

$ diff -u -w --show-function-line="^##"  old new
[...]
@@ -447,6 +458,7 @@ #### dmesg
  -l, --level <list>          restrict output to defined levels
  -n, --console-level <level> set level of messages printed to console
  -P, --nopager               do not pipe output into a pager
+ -p, --force-prefix          force timestamp output on each line of multi-line messages
  -r, --raw                   print the raw message buffer
  -S, --syslog                force to use syslog(2) rather than /dev/kmsg
  -s, --buffer-size <size>    buffer size to query the kernel ring buffer
@@ -2363,6 +2380,7 @@ #### setsid

 Options:
  -c, --ctty     set the controlling terminal to the current one
+ -f, --fork     always fork
  -w, --wait     wait program to exit, and use the same return
  -h, --help     display this help
  -V, --version  display version


cu,
Rudi

      reply	other threads:[~2018-03-22 11:20 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
2018-03-22 11:20     ` Ruediger Meier [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=201803221220.27851.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kzak@redhat.com \
    --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