From: Evan Hunt <ethanol@armory.com>
To: Karel Zak <kzak@redhat.com>
Cc: "Alfred M. Szmidt" <ams@gnu.org>,
P@draigbrady.com, acahalan@gmail.com,
util-linux-ng@vger.kernel.org
Subject: Re: kill
Date: Wed, 20 Dec 2006 20:10:33 -0800 [thread overview]
Message-ID: <20061221041033.GB13134@armory.com> (raw)
In-Reply-To: <20061220235519.GN5971@petra.dvoda.cz>
> Well, from my Linux egoistic point of view there is nothing what I have
> to change with look or cal.
>
> Yes, I don't have care about others systems and it seems that the
> others systems don't have care about look or cal. I really don't see
> anywhere any real request for this change.
Well, I'm currently working on an improved version of look, and would
prefer it to be OS-agnostic rather than living in a package that has
"linux" in its name. So I think moving look out of util-linux(-ng)
and into something more generic would be a good thing to do.
I don't have a personal stake in cal, but I do think, like look, that
it's a widely-useful tool and it seems somewhat odd for it to be grouped
in with tools that are platform-specific.
I'd say the same about several other things in util-linux... col, colcrt,
colrm, column, getopt, hexdump, logger, more, namei, pg, rename, rev,
script, ul, and write all seem quite generic. (Also ddate, though I'd
categorize that as a game rather than a utility anyway.)
eh
next prev parent reply other threads:[~2006-12-21 6:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <787b0d920612192242x3788f4bfh3be846d4188e3767@mail.gmail.com>
2006-12-20 8:57 ` kill (was: Re: util-linux: orphan) Karel Zak
2006-12-20 10:03 ` kill Pádraig Brady
2006-12-20 10:45 ` kill Karel Zak
2006-12-20 21:45 ` kill Alfred M. Szmidt
2006-12-20 23:55 ` kill Karel Zak
2006-12-21 4:10 ` Evan Hunt [this message]
2006-12-21 16:34 ` splitting util-linux (was: kill) Bryan Henderson
2006-12-21 21:53 ` Karel Zak
2006-12-22 6:12 ` Albert Cahalan
2006-12-22 7:13 ` Bryan Henderson
2006-12-22 9:06 ` Albert Cahalan
2006-12-22 7:23 ` Bryan Henderson
2006-12-22 7:45 ` Evan Hunt
2006-12-22 8:07 ` Karel Zak
2006-12-22 8:45 ` Evan Hunt
2006-12-22 11:03 ` Karel Zak
2006-12-22 16:52 ` Evan Hunt
2006-12-22 12:32 ` Ian Kent
2006-12-22 10:24 ` Karel Zak
2006-12-22 14:50 ` Mark Rosenstand
2006-12-22 17:38 ` Albert Cahalan
2006-12-25 20:03 ` Albert Cahalan
2006-12-25 22:50 ` Bryan Henderson
2006-12-22 6:44 ` Bryan Henderson
2006-12-22 7:52 ` Karel Zak
2006-12-21 10:51 ` kill Alfred M. Szmidt
2006-12-21 11:39 ` kill Martin Mares
2006-12-21 15:30 ` kill Karel Zak
2006-12-21 16:50 ` kill Alfred M. Szmidt
2006-12-21 17:38 ` kill Albert Cahalan
2006-12-22 1:37 ` kill Ian Kent
2006-12-20 15:00 ` kill Ian Kent
2006-12-20 16:58 ` kill Albert Cahalan
2006-12-20 16:33 ` kill (was: Re: util-linux: orphan) Albert Cahalan
2006-12-20 21:12 ` Karel Zak
2006-12-21 2:32 ` Albert Cahalan
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=20061221041033.GB13134@armory.com \
--to=ethanol@armory.com \
--cc=P@draigbrady.com \
--cc=acahalan@gmail.com \
--cc=ams@gnu.org \
--cc=kzak@redhat.com \
--cc=util-linux-ng@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