Thanks for your response , Igor.
On 7/21/06, Igor Peshansky wrote:
On Fri, 21 Jul 2006, Hemal Pandya wrote:
> Hello,
>
> If I create a file somefile.exe "outside cygwin" then cygwin reports
> that it is executable. But if the file is created by cygwin then it
> does not become executable unless
On Fri, 21 Jul 2006, Frank Fesevur wrote:
> Hemal Pandya wrote:
> > One implication of this is that when I extract a .zip using cygwin
> > unzip then the .exe, .dll, .bat etc do not get the executable
> > permission.
>
> I'm experiencing similar problems when I download an .exe with wget.
> Since
On Fri, 21 Jul 2006, Hemal Pandya wrote:
> Hello,
>
> If I create a file somefile.exe "outside cygwin" then cygwin reports
> that it is executable. But if the file is created by cygwin then it
> does not become executable unless explicitly set.
This is correct and expected behavior.
> One implic
On Jul 21 11:00, Frank Fesevur wrote:
> Hemal Pandya wrote:
> >If I create a file somefile.exe "outside cygwin" then cygwin reports
> >that it is executable. But if the file is created by cygwin then it
> >does not become executable unless explicitly set.
> >
> >One implication of this is that when
Hemal Pandya wrote:
If I create a file somefile.exe "outside cygwin" then cygwin reports
that it is executable. But if the file is created by cygwin then it
does not become executable unless explicitly set.
One implication of this is that when I extract a .zip using cygwin
unzip then the .exe, .
Hello,
If I create a file somefile.exe "outside cygwin" then cygwin reports
that it is executable. But if the file is created by cygwin then it
does not become executable unless explicitly set.
One implication of this is that when I extract a .zip using cygwin
unzip then the .exe, .dll, .bat etc
6 matches
Mail list logo
