X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=3.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT X-Spam-Check-By: sourceware.org Date: Tue, 8 Jun 2010 20:10:09 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1371374612.20100608201009@mtu-net.ru> To: Eric Blake , cygwin AT cygwin DOT com Subject: Re: 'cp' utility bug when .exe file exist. In-Reply-To: <4C0E662C.7040901@redhat.com> References: <4C0E662C DOT 7040901 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Greetings, Eric Blake! >> As to the "cp" issue, while IMHO, it should go ahead and do the copy, >> a more instructive error message would be helpful: >> >> cp: cannot create regular file `my': File 'my.exe' exists > Huh? Do the copy, then give a failure message? No. A failure message > should only occur if the copy failed. > Did you mean "continue to fail, but make the failure message more > friendly?" I'm pretty sure he did mean exactly that. But I do see the problem in determining exact case of failure to provide such informative error message. -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 08.06.2010, <20:04> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple