Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <40EDF623.AF728A26@dessent.net> Date: Thu, 08 Jul 2004 18:34:27 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Wrapping long lines (Was Re: FAQ update suggestion for "I'm having basic problems with find. Why?") References: <010701c464f4$398e2030$4e6510ac AT ds DOT tao DOT co DOT uk> <013301c464fe$e2e425d0$4e6510ac AT ds DOT tao DOT co DOT uk> <40EDEF6B DOT A5A5F06 AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Eduardo Chappa wrote: > :) It's just like HTML email - can I read it? Yes. Do I want it in my > :) inbox? Heck no. Just because you can do something doesn't mean you > :) should. > > Yes, you should read the definition of SHOULD in an RFC, did you do it, > no. Next time look for a better argument to support your point. Nowhere did I claim that SHOULD was equivalent to MUST. And yes I know the difference. My point was simply that if a RFC describes a normative procedure then that lends weight to the argument that if at all possible, you should do it that way. Read my last line again, "Just because you can do something [send emails with long lines] doesn't mean you should [because the standards ask that you not]". Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/