Re: Checking XCOPY Exit Value in Cygwin Bash

On Sun, Aug 06, 2006 at 08:26:11PM -0800, Shane wrote: >> What's wrong with "cp -a" or "cp -r"? >It only copied files that were directly under the source directory. It >didn't traverse the directories inside source recursively. I did some >searching and, I came up with a similar thread. Finally

Re: Checking XCOPY Exit Value in Cygwin Bash

> What's wrong with "cp -a" or "cp -r"? It only copied files that were directly under the source directory. It didn't traverse the directories inside source recursively. I did some searching and, I came up with a similar thread. Finally the tar method was recommended in it too. Please refer : htt

Re: Checking XCOPY Exit Value in Cygwin Bash

On Mon, Aug 07, 2006 at 06:52:40AM +0900, Shane wrote: >Christopher Faylor wrote: >>Is there some reason why you are not using "cp" to accomplish your >>task? "cp --help" should provide you with all sorts of options for >>copying files. You should be able to press "cp" into service for this. >> >

Re: Checking XCOPY Exit Value in Cygwin Bash

Christopher Faylor wrote: Is there some reason why you are not using "cp" to accomplish your task? "cp --help" should provide you with all sorts of options for copying files. You should be able to press "cp" into service for this. Using DOS utilities and DOS paths for this type of thing is putt

Re: Checking XCOPY Exit Value in Cygwin Bash

Igor Peshansky wrote: As David said, cvs has an easy way of doing this (using "cvs diff" and "patch"), which will also deal with local and checked in changes to the same file (while your method won't). Point taken. I will certainly look into it. Did you happen to notice the mention of the "

Re: installer: select packages: text background color

On Sun, 6 Aug 2006, Eric Blake wrote: > > A display bug was introduced about a year ago in the "Select Packages" > > screen of Cygwin's installer. The text's background color is manually > > set to white but the text's color relies upon the system's settings > > for "Window Text." > > This bug wa

Re: Checking XCOPY Exit Value in Cygwin Bash

On Sun, Aug 06, 2006 at 07:46:07AM -0800, Shane wrote: >I am writing a automated build script for my project that will be run >under cygwin. I will copy my updated source files to the build >directory and if there are updated files, the executables will be >built. To copy the source files, I had

Re: Checking XCOPY Exit Value in Cygwin Bash

On Mon, 7 Aug 2006, Shane wrote: > What I am trying to do is, checkout the source to the build directory > and if there are any local changes in my working directory copy them to > the build directory, build and do a test run from there. This is so that > I can test my code before I do the actual

Re: installer: select packages: text background color

On Sun, Aug 06, 2006 at 06:46:52PM +, Eric Blake wrote: > > This bug was also reported about a year ago, and fixed about a year > ago. Great, thanks. > See http://cygwin.com/setup/snapshots/ for a snapshot with > the fix incorporated, and then join the crusade to get the snapshot > tested t

Re: installer: select packages: text background color

> A display bug was introduced about a year ago in the "Select Packages" > screen of Cygwin's installer. The text's background color is manually > set to white but the text's color relies upon the system's settings > for "Window Text." This bug was also reported about a year ago, and fixed ab

Re: installer: select packages: text background color

Greetings: A display bug was introduced about a year ago in the "Select Packages" screen of Cygwin's installer. The text's background color is manually set to white but the text's color relies upon the system's settings for "Window Text." No one has noticed this change because most users have

Re: Checking XCOPY Exit Value in Cygwin Bash

David Christensen wrote: There are standard software development tools that solve the problems you are facing -- CVS and Make: http://ximbiot.com/cvs/wiki/index.php?title=Main_Page http://ximbiot.com/cvs/wiki/index.php?title=Main_Page Both are included in Cygwin. In the long run, you

RE: Checking XCOPY Exit Value in Cygwin Bash

Shane wrote: > I am writing a automated build script for my project that will be run > under cygwin. I will copy my updated source files to the build > directory and if there are updated files, the executables will be > built. To copy the source files, I had to use XCOPY since the > directory struc

Re: Checking XCOPY Exit Value in Cygwin Bash

Igor Peshansky wrote: Nope, you didn't have to. Something like (cd "$2/.." && find "$2" -name "*.$1" | tar cfT - -) | tar xfC - "$3" would do the job of "XCOPY /S" using POSIX means. If you go POSIX, you can use the --keep-newer-files tar option. Of course it didn't. Please read a go

RE: NTFS fragmentation

-Original Message- >From: Robert Pendell >Sent: Saturday, August 05, 2006 7:50 PM >To: Cygwin Mailing List >Subject: Re: NTFS fragmentation > > >Vladimir Dergachev wrote: > > Also, I tried the following experiment - found a 17 MB file in >ibiblio.org and >> downloaded it with Firefox. The f

Re: Checking XCOPY Exit Value in Cygwin Bash

On 8/6/06, Shane wrote: Can you please provide me a way of checking the XCOPY exit code: reference [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/xcopy.mspx?mfr=true] within Bash? result codes are stored in $? in bash success = 0 usually, and xcopy seems to fo

Re: Checking XCOPY Exit Value in Cygwin Bash

On Sun, 6 Aug 2006, Shane wrote: > Hi all, Hi. . Reading the one-line below was extremely painful in the web archives. See for yourself: . >I am writing a automated build script for my project tha

Checking XCOPY Exit Value in Cygwin Bash

Hi all, I am writing a automated build script for my project that will be run under cygwin. I will copy my updated source files to the build directory and if there are updated files, the executables will be built. To copy the source files, I had to use XCOPY since the directory structure

Re: [ANNOUNCEMENT] clisp-2.39-1 released

Dr. Volker Zell schrieb: Reini Urban writes: > I've taken over clisp maintainance from Sam Steingold, who lost access > to his windows box and to this list. Thanks Sam for a wonderful job > anyway! > clisp-2.39-1 is now built with cygport, but you can still compile it > with

Re: running cygwin bash scripts from apache

Thank you Rene and Max for your replies. Rene's response did the trick: > Did you put the script in Apache's cgi-bin directory? Once I put it there, the script works ok. Much to my relief. Thanks for the tip that I can configure Apache to run scripts from other places to - that might come in h