public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com>
To: esr@thyrsus.com
Cc: Mark Galassi <rosalia@galassi.org>,
	Docbook Tools discussion list
	<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: new tools coming and a couple of renamings
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <kp3dl3ekut.fsf@dagon.conectiva> (raw)
In-Reply-To: <20000721032257.F14571@thyrsus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

>>>>> "esr" == esr  <esr@thyrsus.com> writes:

    esr> Seriously, I would probably be firm that it ain't worth the
    esr> hassle if it weren't for the fact that that "db" prefix looks
    esr> like it has something to do with databases.  Removing
    esr> ambiguity is good.  On the other hand, it's proper Unix
    esr> tradition to have short names for a reason -- it saves typing
    esr> for hapless fumble-fingers like me.

C'mon Eric!

You can make aliases for these commands. It will only cost you extra
typing once. :-) 

Unix is wonderful in it's resources. Let's not just worry with long
names if it can be solved with extra aliases. 

Another ambiguity that was solved by choosing this name is the
association with IBM's DB2. 


See you,
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.

  reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Mark Galassi
2000-12-27  6:36 ` Bill Brooks
2000-12-27  6:36   ` Mark Galassi
2000-12-27  6:36     ` Eric Bischoff
2000-12-27  6:36 ` Norman Walsh
2000-12-27  6:36 ` esr
2000-12-27  6:36   ` Jorge Godoy [this message]
2000-12-27  6:36   ` Eric Lee Green
2000-12-27  6:36   ` Sylvan Ravinet
2000-07-21  0:08     ` Sylvan Ravinet
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Gregory Leblanc

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=kp3dl3ekut.fsf@dagon.conectiva \
    --to=godoy@conectiva.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=esr@thyrsus.com \
    --cc=rosalia@galassi.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).