From: teg@redhat.com (Trond Eivind Glomsrød)
To: Adam Spiers <adam@spiers.net>
Cc: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: adding a toplevel zsh.spec.in file
Date: 17 Jul 2000 22:32:20 -0400 [thread overview]
Message-ID: <xuy1z0sb22z.fsf@hoser.devel.redhat.com> (raw)
In-Reply-To: Adam Spiers's message of "Tue, 18 Jul 2000 00:35:28 +0100"
Adam Spiers <adam@spiers.net> writes:
> > I think it is much better to put them on the
> > web page where they can clearly be labeled as what they are.
>
> Or in the example startups, but commented out. Remember, if we
> provide a decent set of RedHat (say) startup scripts, it's likely that
> within two years every recent RedHat box will have them installed, and
> most people aren't going to be looking at the zsh web site when
> they're editing them.
If you want to coordinate spec files, that's fine with me.
If there are any suggestions on changes to be made on them, feel free
to contact me.
--
Trond Eivind Glomsrød
Red Hat, Inc.
next prev parent reply other threads:[~2000-07-18 2:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 11:53 Adam Spiers
2000-07-07 12:45 ` Peter Stephenson
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56 ` Adam Spiers
2000-07-07 17:18 ` Bart Schaefer
2000-07-07 17:44 ` Zefram
2000-07-07 18:18 ` Bart Schaefer
2000-07-17 15:09 ` Adam Spiers
2000-07-17 17:48 ` Bart Schaefer
2000-07-17 18:07 ` Adam Spiers
2000-07-17 21:05 ` Oliver Kiddle
2000-07-17 23:35 ` Adam Spiers
2000-07-18 2:32 ` Trond Eivind Glomsrød [this message]
2000-07-18 6:01 ` Bart Schaefer
2000-07-18 1:56 ` PATCH: " Zefram
2000-07-18 5:22 ` Bart Schaefer
2000-07-18 6:15 ` Wayne Davison
2000-07-18 8:31 ` How to distribute skeleton zshrc etc. (Re: PATCH: Re: adding a toplevel zsh.spec.in file) Bart Schaefer
2000-07-18 16:54 ` PATCH: Re: adding a toplevel zsh.spec.in file Trond Eivind Glomsrød
2000-07-18 6:25 ` Andrej Borsenkow
2000-07-18 9:42 ` Peter Stephenson
2000-07-18 18:22 ` Trond Eivind Glomsrød
2000-07-18 19:57 ` Zefram
2000-07-18 20:07 ` Trond Eivind Glomsrød
2000-07-18 20:37 ` Zefram
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=xuy1z0sb22z.fsf@hoser.devel.redhat.com \
--to=teg@redhat.com \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).