Linux console tools development discussion
 help / color / mirror / Atom feed
From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: balint@balintreczey.hu,
	Linux console tools development discussion
	<kbd@lists.altlinux.org>
Subject: Re: [kbd] [PATCH] kbd_mode: Add -f option and deny dangerous mode switches without it
Date: Mon, 17 Jun 2019 10:40:40 +0200
Message-ID: <20190617084040.GJ8901@Legion-PC.fortress> (raw)
In-Reply-To: <CAK0OdpzpkPpRbJTy9g4dfXpzdSjfg3jBEgSf+_xh_6COcvnPQA@mail.gmail.com>

On Wed, Jun 12, 2019 at 03:05:57PM +0200, Bálint Réczey wrote:
> Hi Alexey,
> 
> Alexey Gladkov <gladkov.alexey@gmail.com> ezt írta (időpont: 2019.
> máj. 8., Sze, 11:19):
> >
> > On Tue, Apr 23, 2019 at 05:38:07PM +0200, Balint Reczey wrote:
> > > kbd_mode(1) already had a warning but kbd_mode still performed all
> > > mode changes even when they made keyboards unusable.
> > >
> > > The added flag let's the callers try safe changes or force the risky
> > > ones. This change may break scripts but the broken scripts most likely
> > > made the keyboard unusable and should be updated.
> > >
> > > Original bug report at:
> > > https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/520546
> > >
> > > Signed-off-by: Balint Reczey <balint.reczey@canonical.com>
> >
> > It sounds sane. Applied. Thanks!
> 
> Thanks!
> 
> When do you plan making the next release?
> It would be nice to have this change widely tested in distributions.
> Debian starts a new release cycle soon and Ubuntu is around the middle
> of the LTS cycle, too, thus we could start testing a new kbd release
> soon.

I'm planning a new release at the end of the month or the beginning of the
next.

-- 
Rgrds, legion



      reply	other threads:[~2019-06-17  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 15:38 Balint Reczey
2019-05-08  9:19 ` Alexey Gladkov
2019-06-12 13:05   ` Bálint Réczey
2019-06-17  8:40     ` Alexey Gladkov [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=20190617084040.GJ8901@Legion-PC.fortress \
    --to=gladkov.alexey@gmail.com \
    --cc=balint@balintreczey.hu \
    --cc=kbd@lists.altlinux.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

Linux console tools development discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/kbd/0 kbd/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kbd kbd/ http://lore.altlinux.org/kbd \
		kbd@lists.altlinux.org kbd@lists.altlinux.ru kbd@lists.altlinux.com
	public-inbox-index kbd

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.kbd


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git