[CentOS] Re: Centos 5 timeline?

Mon Apr 9 14:24:51 UTC 2007
Bisbal, Prentice <PBisbal at LexPharma.com>

Why not? 

;)  


Prentice 

-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Akemi Yagi
Sent: Thursday, April 05, 2007 2:26 PM
To: centos at centos.org
Subject: [CentOS] Re: Centos 5 timeline?

On Thu, 05 Apr 2007 10:54:47 -0700, Peter Serwe wrote:

> The list now needs a 'READ THIS FAQ BEFORE YOU POST' page somewhere..
> 
> That includes the most commonly asked questions like:
> 
> "When will CentOS 5 be released?"
> 
> "When will kernel support for XX be included?"
> 
> "Why is it CentOS isn't like Fedora Core?"
> 
> "How do I create a virtual domain in Apache?"
> 
> And my absolute favorite portion of any List-FAQ is the part about:
> 
> "Is the post you're about to make relevant to the list's stated 
> purpose, and is it formulated as an answerable question: A beginner's 
> guide to list etiquette, clear thinking, and formulation of the
question."
> 
> Because, proper formulation of the question often presents the answer.
> 
> Peter
> 
> 
> Matt Shields wrote:
>> No, it was his lame attempt at sarcasm, probably directed at my 
>> earlier reply to someone else asking the same redundant question that

>> keeps getting asked over and over.
>>
>> Seems we have new people joining everyday the list just to ask the 
>> question, when will CentOS5 be released.
>>
>> Matt
>>

If I am allowed to add one more thing:

Please do not top-post.

Akemi



_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos




The contents of this communication, including any attachments, may be confidential, privileged or otherwise protected from disclosure.  They are intended solely for the use of the individual or entity to whom they are addressed.  If you are not the intended recipient, please do not read, copy, use or disclose the contents of this communication.  Please notify the sender immediately and delete the communication in its entirety.