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 From: ericblake AT comcast DOT net (Eric Blake) To: Jason Pyeron , cygwin AT cygwin DOT com Subject: Re: xargs and upstream bug? Date: Mon, 19 Sep 2005 19:02:03 +0000 Message-Id: <091920051902.24857.432F0B2A000B52E00000611922064244130A050E040D0C079D0A@comcast.net> > > just checking to see if is just a cygwin issue or is up stream. > > http://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=14587 Well, seeing as how it is a bug in the upstream database, it must be upstream :) See also my report at http://lists.gnu.org/archive/html/bug-findutils/2005-08/msg00037.html POSIX requires -L, and requires -L to take an argument (ie. it is not optional). GNU xargs also provides -l as a synonym, except that with -l, the argument is optional and defaults to 1. > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you > have received it in error, purge the message from your system and > notify the sender immediately. Any other use of the email by you > is prohibited. Trailers like this in public forums are impossible to enforce, consider using an email account where such trash isn't appended to your email. -- Eric Blake -- 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/