Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <014f01c0af53$fae32370$0200a8c0@lifelesswks> From: "Robert Collins" To: "Mark Allan Young" , References: Subject: Re: Two questions: Moving Directories, Ctrl-Z Date: Sun, 18 Mar 2001 13:34:37 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 18 Mar 2001 02:28:53.0920 (UTC) FILETIME=[2D0AC200:01C0AF53] Use the source Mark! Your $.02 would rapidly become $completed and done the way you want it. Wanting something different is vastly different from helping make it different. One possible reason that chris has said "don't do that" is that the error may not be conclusive. I.E. cygwin might see (whatever it is) the status code and be able to successfully copy the files appropriately. So the logic may not be trivial, or it may be straightforward but you've run into the scheduling problem. A) IMO this is a low low priority issue. It works today with the usual windows semantics. I.e. try this under explorer.exe or cmd.exe or command.com and it copies and then errors at the end. B) Chris isn't hired to code. Tough to believe I know, but check the list archives. C) AFAIK only Corinna is full-time on cygwin development, and I'm sure that RedHat's paying clientele would have some persuasive arguments as to why their requests should get attended to first. D) As you have the tools to investigate this yourself, you could attempt that. The list _is helpful_ to people trying to contribute patchs. (Check the archives if you don't believe me). Rob ----- Original Message ----- From: "Mark Allan Young" To: Sent: Sunday, March 18, 2001 1:22 PM Subject: RE: Two questions: Moving Directories, Ctrl-Z > > On Fri, Mar 16, 2001 at 07:16:31PM -0800, Mark Allan Young wrote: > > >> On Fri, Mar 16, 2001 at 04:44:31PM -0800, Mark Allan Young wrote: > > >> >One thing I've noticed that changed with our recent upgrade > > >> >to 1.1.8 was that moving a directory now seems to perform a copy > > >> >and remove rather than just renaming a directory. Is there a way > > >> >to just force the rename? what's the benefit of the copy over the > > >> >rename? > > >> > > >> I just tried this. An "mv" in cygwin moves the directory without > > >> copying. > > >> > > >> If it isn't doing this for you we'll need details. > > > > > >I tried this again and it started to do a copy... > > > > > >then I looked around my system and found another cygwin window > > >opened to a directory within the directory that I was trying to > > >move. > > > > Ok. The official answer to this problem is "Don't do that." > > Doesn't seem right to me. I'd rather it not take several minutes > to copy a large directory... As I said in my previous message, if > the command knows enough to realize that it must do a recursive > copy/unlink, I'd rather it just say "Can't." or "Won't." or even > "EFILEBUSY" :-). > > my $.02, for whatever it's worth... > > ...myoung > > > -- > Want to unsubscribe from this list? > Check out: http://cygwin.com/ml/#unsubscribe-simple > > -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple