Util-Linux package development
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 0/5] pull: five mutually unrelated changes
Date: Sun, 16 Jul 2017 10:25:57 -0500	[thread overview]
Message-ID: <596B8585.2060405@gmail.com> (raw)
In-Reply-To: <CAG27Bk0TFAUb_cDv9fADiFpVzwP_fboUP6o9ZrZELQiCa=Vq3Q@mail.gmail.com>

Sami Kerola wrote:
> On 15 July 2017 at 23:45, Bruce Dubbs <bruce.dubbs@gmail.com> wrote:
>>> The 'big' change in this pull request is to drop reset(1) from util-linux.
>>> I don't think there is any point of keep this script hanging around.
>>
>> Why do you think that.  I find it useful when some application corrupts the
>> screen.  I realize that reset is a symlink to tset, but I find reset easier
>> to remember/use.
>
> The ncurses package contains both binaries tput(1) and reset(1). So this
> script will not work without ncurses, and the very same package has the
> binary that obsoletes the script.

Thanks.  I agree that duplicate functions should be removed.

   -- Bruce


  reply	other threads:[~2017-07-16 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 21:20 [PATCH 0/5] pull: five mutually unrelated changes Sami Kerola
2017-07-15 21:20 ` [PATCH 1/5] reset: remove script from the package Sami Kerola
2017-07-15 21:20 ` [PATCH 2/5] ldattach: simplify debugging function when vwarnx(3) is available Sami Kerola
2017-07-15 21:20 ` [PATCH 3/5] docs: add optional option back to struct option Sami Kerola
2017-07-15 21:20 ` [PATCH 4/5] uuidparse: add bash-completion file Sami Kerola
2017-07-15 21:20 ` [PATCH 5/5] bash-completion: make completions to work when bash set -u is in use Sami Kerola
2017-07-15 22:45 ` [PATCH 0/5] pull: five mutually unrelated changes Bruce Dubbs
2017-07-16  9:08   ` Sami Kerola
2017-07-16 15:25     ` Bruce Dubbs [this message]
2017-07-17  9:28       ` Karel Zak
2017-07-17 10:04 ` 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=596B8585.2060405@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=kerolasa@gmail.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