All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-wireless@vger.kernel.org,
	util-linux <util-linux@vger.kernel.org>
Subject: Re: rfkill(8) move and improvements
Date: Fri, 30 Jun 2017 09:47:29 +0200	[thread overview]
Message-ID: <20170630074729.s3gknfobabgepk4h@ws.net.home> (raw)
In-Reply-To: <CAG27Bk0tKzqxkm6qqjGO6GJE7vxReRAQbvYGexjp+PBLo+RK_A@mail.gmail.com>

On Thu, Jun 29, 2017 at 10:23:12PM +0100, Sami Kerola wrote:
> On 29 June 2017 at 15:04, Johannes Berg <johannes@sipsolutions.net> wrote:
> >> The otherday I ran powertop and it did rfkill to save battery, which
> >> was particularly annoying because I had not installed rfkill(8)
> >> package.
> >> Fixing the immediate issue was relatively easy, but the ordeal made
> >> me wonder if this tool could be moved to a package that is installed
> >> by default to all systems, such as util-linux.
> >
> > [...]
> >
> >> What do you think, would the move and proposed updates be ok?
> >
> > I can't say I mind, and most of your proposed changes seem sensible,
> > though I haven't reviewed them in enough detail to comment on them.
> > Something that caught my eye here was comparing a string to _("all")
> > which seems wrong, since that'd mean you'd have to type the translated
> > version even on the command line? That seems really awkward (to put it
> > charitably).
> >
> > However, at the same time, I have very little desire to get involved
> > with util-linux as yet another project, so frankly I'd probably
> > continue to "maintain" the current rfkill tool - which really hasn't
> > changed in a very long time, and hope somebody else picks up
> > maintenance of rfkill included in util-linux.
> 
> Hello Johannes,
> 
> Thank you for feedback. I removed the rfkill command strings from
> translations, and gave hint to translators how to deal with them in
> usage() output. Also in same go updates are rebased on top of
> most recent upstream to get usage() --help and --version handling
> done correctly.
> 
> What comes  to maintenance I am fairly optimistic util-linux is a
> good home for the rfkill. Karel, what do you think?

I have no problem with it, if Johannes agree with this step. We have
definitely manpower to maintain it.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2017-06-30  7:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-25 13:04 rfkill(8) move and improvements Sami Kerola
2017-06-29 14:04 ` Johannes Berg
2017-06-29 21:23   ` Sami Kerola
2017-06-30  7:47     ` Karel Zak [this message]
2017-07-01  9:06       ` Sami Kerola
2017-08-30 19:40         ` Sami Kerola
2017-08-31  9:46           ` Karel Zak
2017-08-31  9:47           ` Karel Zak

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=20170630074729.s3gknfobabgepk4h@ws.net.home \
    --to=kzak@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=kerolasa@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --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.