zsh-workers
 help / color / mirror / code / Atom feed
From: Zefram <zefram@fysh.org>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-workers@sunsite.dk
Subject: Re: Module namespaces? RE: PATCH: zftp/tcp abstraction
Date: Wed, 6 Jun 2001 17:37:43 +0100 (BST)	[thread overview]
Message-ID: <E157gJT-0002Wf-00@bowl.fysh.org> (raw)
In-Reply-To: <003601c0eea6$7e5315d0$21c9ca95@mow.siemens.ru> from Andrej Borsenkow at "Jun 6, 2001 08:34:01 pm"

Andrej Borsenkow wrote:
>What is the module nameing policy? It is somewhat silly to invent
>hierarchical module namespace and put all modules under the same hood.

My intention was that the first part of the hierarchical name identify
the publisher of the module.  For example, there could hypothetically
be a module named "redhat/foo" published by Red Hat.  The "zsh/" prefix
is intended for all (and only) modules published by the Zsh Development
Group.

-zefram


  reply	other threads:[~2001-06-06 16:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06 16:26 Clint Adams
2001-06-06 16:34 ` Module namespaces? " Andrej Borsenkow
2001-06-06 16:37   ` Zefram [this message]
2001-06-06 18:07     ` Peter Stephenson
2001-06-06 19:12       ` Clint Adams
2001-06-07  8:13 ` Andrej Borsenkow
2001-06-07  9:41   ` Modules dependencies " Andrej Borsenkow
2001-06-07 10:00     ` Peter Stephenson
2001-06-07 10:18     ` Zefram
2001-06-07 13:16       ` Sven Wischnowsky
2001-06-07 13:35         ` Andrej Borsenkow
2001-06-07 15:31           ` Bart Schaefer
2001-06-14  9:33             ` Andrej Borsenkow
2001-06-26 11:26       ` Andrej Borsenkow
2001-06-26 16:33         ` Bart Schaefer
2001-06-30 11:24           ` Zefram
2001-06-27 13:49       ` Clint Adams
2001-06-27 13:59         ` Peter Stephenson
2001-06-27 14:10           ` Andrej Borsenkow
2001-06-27 14:19             ` Peter Stephenson
2001-06-27 18:42           ` Bart Schaefer

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=E157gJT-0002Wf-00@bowl.fysh.org \
    --to=zefram@fysh.org \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.dk \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).