All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Daubert <jue@jue.li>
To: util-linux@vger.kernel.org
Subject: Re: [bug] logger 2.26: regression, option -i not combinable with other options
Date: Fri, 20 Feb 2015 13:44:36 +0100	[thread overview]
Message-ID: <20150220124436.GA18236@jue.netz> (raw)
In-Reply-To: <20150220104106.GB19430@ws.net.home>

On Fri, Feb 20, 2015 at 11:41:06AM +0100, Karel Zak wrote:
> On Fri, Feb 20, 2015 at 11:06:47AM +0100, Juergen Daubert wrote:
> > with logger from util-linux 2.25.x it's possible to combine the option
> > -i with other options like:
> > 
> >  logger -is
> > 
> > with 2.26 I get the following error message:
> > 
> >  $:~> logger -is
> >  logger: failed to parse id: 's'
> > 
> > The changed behaviour breaks existing scripts like dhcpcd-run-hooks [1]
> > from dhcpcd [2].
> 
> Hmm... stupid regression, next time it would be probably better to
> introduce optional arguments for long options only.
> 
> Anyway, always use long options in scripts. It's more robust and more
> readable.

here's the response from dhcpcd's author:

 The original BSD sources from which logger is clearly based don't support
 long options .... and dhcpcd needs to work with them. 


Greetings
Juergen

  reply	other threads:[~2015-02-20 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 10:06 [bug] logger 2.26: regression, option -i not combinable with other options Juergen Daubert
2015-02-20 10:41 ` Karel Zak
2015-02-20 12:44   ` Juergen Daubert [this message]
2015-02-20 20:12     ` Sami Kerola
2015-02-21 11:37       ` Benno Schulenberg
2015-02-21 15:28         ` Sami Kerola
2015-03-05 10:21 ` Karel Zak
  -- strict thread matches above, loose matches on Subject: below --
2015-02-20 10:02 Juergen Daubert

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=20150220124436.GA18236@jue.netz \
    --to=jue@jue.li \
    --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.