This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Checking XCOPY Exit Value in Cygwin Bash
- From: Shane <wolfpack at inbox dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 6 Aug 2006 20:26:11 -0800
- Subject: Re: Checking XCOPY Exit Value in Cygwin Bash
- References: <44d664a8.30904@inbox.com> <20060806203655.gc30223@trixie.casa.cgf.cx> <74382bafeaa.000000d2wolfpack@inbox.com>
> 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 : http://lists.samba.org/archive/samba/1999-December/016328.html and it's follow-ups.
Thanks and Regards
Shane
> -----Original Message-----
> From: cgf-no-personal-reply-please@cygwin.com
> Sent: Sun, 6 Aug 2006 21:04:27 -0400
> To: cygwin@cygwin.com
> Subject: 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.
>>>
> >>Using DOS utilities and DOS paths for this type of thing is putting you
> >>on the fringes of support for Cygwin. I really wouldn't recommend it.
> >>Clearly this is not such a Windows-specific problem that it outside of
> >>the capabilities of a UNIX solution.
>>
> >My initial attempt was with cp. But I didn't see a way of preserving
> >the original directory structure of the source dir,
>
> What's wrong with "cp -a" or "cp -r"?
>
> --
> 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/
--
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/