X-Spam-Check-By: sourceware.org Date: Thu, 31 Aug 2006 11:14:27 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Re: Problem when using variable assignment, backticks in shell script Message-ID: <20060831151427.GB8968@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <40C729A4D292F64DA98AE016BBA9FFA7DA3D82 AT HHBRUE005 DOT hq DOT corp DOT eurocontrol DOT int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40C729A4D292F64DA98AE016BBA9FFA7DA3D82@HHBRUE005.hq.corp.eurocontrol.int> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Thu, Aug 31, 2006 at 05:04:08PM +0200, CARTER Alan wrote: >>Hmm... 9 lines of content, 10 of disclaimer... *sip!* Eew, and the >>disclaimer isn't even line-wrapped... > >>(How come PCYMTNILOAUD is not on the OLOCA yet? ;-)) > >Ah. You think I typed that, myself? I didn't. It was automatically >appended by the local email system. Many corporate email systems do >this kind of thing, because (IMHO) the people that run them are more >concerned with posturing within their own value system (which does not >map to reality) than they are with doing anything useful. Whether you typed it yourself or not, those type of disclaimers are actually not allowed in mail to mailing lists at this site: http://sourceware.org/lists.html The same thing holds true for gcc.gnu.org. cygwin.com == sourceware.org == gcc.gnu.org Please find some other way of sending email which does not try to enforce some kind of faux-legal obligations on the reader. cgf -- 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/