From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: overseers@gcc.gnu.org
Cc: Christopher Faylor <cgf@redhat.com>, Ian Lance Taylor <ian@airs.com>
Subject: Re: /www/conf/httpd.conf
Date: Wed, 07 May 2003 21:59:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305072354250.80821@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <m3smrqe91q.fsf@gossamer.airs.com>
On Wed, 7 May 2003, Christopher Faylor wrote:
> I keep meaning to look into checking httpd.conf into cvs. There's no
> real reason why we couldn't just put this in, say,
> /sourceware/infra/httpd or something and use the standard mechanism
> for updating it right?
Hmm, that'd be the first such update procedure running as root. (Also,
wouldn't this de facto expose root privilege to many more users?)
On Wed, 7 May 2003, Ian Lance Taylor wrote:
> Whoops, sorry. I looked for a CVS directory or a ,v file, but I
> certainly should have looked for an RCS directory.
No problem. Being a CVS user most of the time, this allowed me to brush
up my RCS skills again. ;-)
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-07 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 21:02 /www/conf/httpd.conf Gerald Pfeifer
2003-05-07 21:06 ` /www/conf/httpd.conf Christopher Faylor
2003-05-08 6:14 ` /www/conf/httpd.conf Jason Molenda
2003-05-08 14:38 ` /www/conf/httpd.conf Christopher Faylor
2003-05-08 18:03 ` /www/conf/httpd.conf Jason Molenda
2003-05-07 21:18 ` /www/conf/httpd.conf Andrew Cagney
2003-05-07 22:05 ` /www/conf/httpd.conf Gerald Pfeifer
2003-05-07 22:15 ` /www/conf/httpd.conf Andrew Cagney
2003-05-07 21:33 ` /www/conf/httpd.conf Ian Lance Taylor
2003-05-07 21:59 ` Gerald Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 20:38 /www/conf/httpd.conf Gerald Pfeifer
2003-03-27 1:04 ` /www/conf/httpd.conf Christopher Faylor
2003-03-27 1:14 ` /www/conf/httpd.conf Gerald Pfeifer
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=Pine.BSF.4.55.0305072354250.80821@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=cgf@redhat.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.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).