From: Chmouel Boudjnah <chmouel@mandrakesoft.com>
To: Wayne Davison <wayned@users.sourceforge.net>
Cc: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
Zsh Workers <zsh-workers@sunsite.dk>, <cooker@linux-mandrake.com>
Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
Date: 21 May 2001 15:40:37 +0100 [thread overview]
Message-ID: <m31ypi3guy.fsf@giants.mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0105200203090.12390-100000@phong.blorf.net> (Wayne Davison's message of "Sun, 20 May 2001 02:10:39 -0700 (PDT)")
Wayne Davison <wayned@users.sourceforge.net> writes:
> No, it's not overkill, it's the vital part of the puzzle that makes
> using /etc/skel work. In the past when I (and others) have suggested
> using /etc/skel, the packagers have said "what about existing users?"
> and then they put the commands into a global init file so that it
> affects everyone, old and new users alike. Having all packages that
> install /etc/skel files give the files to existing users (safely)
> would take away this objection.
and how do you do when you have to modify the skel file on upgrade ?
next prev parent reply other threads:[~2001-05-21 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 18:19 Andrej Borsenkow
2001-05-19 20:26 ` Bart Schaefer
2001-05-19 21:51 ` Wayne Davison
2001-05-20 8:11 ` Andrej Borsenkow
2001-05-20 9:10 ` Wayne Davison
2001-05-21 14:40 ` Chmouel Boudjnah [this message]
2001-05-21 14:29 ` Clint Adams
2001-05-21 15:37 ` Chmouel Boudjnah
2001-05-21 15:15 ` Clint Adams
2001-05-21 17:06 ` Oliver Kiddle
2001-05-21 17:12 ` Chmouel Boudjnah
2001-05-21 17:24 ` Andrej Borsenkow
2001-05-21 18:27 ` Chmouel Boudjnah
2001-05-21 15:50 ` Bart Schaefer
2001-05-21 18:17 ` Wayne Davison
2001-05-21 18:29 ` Andrej Borsenkow
2001-05-21 19:07 ` Bart Schaefer
2001-05-21 19:21 ` Chmouel Boudjnah
2001-05-21 10:54 ` [Cooker] " Chmouel Boudjnah
2001-05-20 18:26 ` Trond Eivind Glomsrød
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=m31ypi3guy.fsf@giants.mandrakesoft.com \
--to=chmouel@mandrakesoft.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=cooker@linux-mandrake.com \
--cc=wayned@users.sourceforge.net \
--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).