Re: Issues encountered with new Cygwin version

2015-09-27 Thread Walter L.
On 9/27/2015 5:54 AM, Andrey Repin wrote: Greetings, Walter L.! My question was merely based on Andrey's statement that "This is configurable" (see above); I don't know what he meant and what "this" is, Git or Cygwin. "This" being "Git", and

Re: Issues encountered with new Cygwin version

2015-09-26 Thread Walter L.
On 9/26/2015 6:10 PM, Ken Brown wrote: > On 9/26/2015 5:05 AM, Andrey Repin wrote: > > > Greetings, Walter L.! > > > > > This is very unfortunate because I'm using Git in Cygwin > > > specifically because it doesn't set the executable bit like Wi

Re: Issues encountered with new Cygwin version

2015-09-26 Thread Walter L.
On 9/26/2015 5:05 AM, Andrey Repin wrote: Greetings, Walter L.! > This is very unfortunate because I'm using Git in Cygwin specifically > because it doesn't set the executable bit like Windows applications. This is, you know, configurable?... Which part? Git or Cygwin

Re: Issues encountered with new Cygwin version

2015-09-25 Thread Walter L.
On 9/25/2015 2:24 PM, Ken Brown wrote: Why not just run 'setfacl -b' once and for all on whatever directory you do your work in? Is it under your home directory? Do you have default ACL entries on your home directory that are then inherited by every subdirectory you create? Ken Actually yes

Re: Issues encountered with new Cygwin version

2015-09-25 Thread Walter L.
On 9/25/2015 12:04 PM, Ken Brown wrote: > I think you misunderstood what Marco was saying. If the problem is > caused by the default ACL on the directory, you could fix that ACL. To elaborate on this, observe the following: Hi Ken, thanks for the clarification. I understood what Marco meant

Re: Issues encountered with new Cygwin version

2015-09-25 Thread Walter L.
On 24/09/2015 07:35, Marco Atzeri wrote: > 2) The 'touch' command creates a file with the executable bit set > > [user@hostname ~]$ touch newfile.txt > [user@hostname ~]$ ls -l newfile.txt > -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt It likely depends on the inherited permission

Re: Issues encountered with new Cygwin version

2015-09-24 Thread Walter L.
> > > > I believe the target of the symlink should be "protocol" (i.e. > > > > singular) > > > > > > Err. That is. How did no one found it earlier? > > --- > > Because it is plural on unix/linux? MS seems to have misspelt it? > > I believe it's "misspelt" due to the 8 character limit for lega

Re: Issues encountered with new Cygwin version

2015-09-23 Thread Walter L.
> > I believe the target of the symlink should be "protocol" (i.e. > > singular) > > Err. That is. How did no one found it earlier? --- Because it is plural on unix/linux? MS seems to have misspelt it? I believe it's "misspelt" due to the 8 character limit for legacy file names, and the wei

Re: Issues encountered with new Cygwin version

2015-09-23 Thread Walter L.
Thanks for the quick response! > 2) The 'touch' command creates a file with the executable bit set > [user@hostname ~]$ touch newfile.txt > [user@hostname ~]$ ls -l newfile.txt > -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt > I am fully aware that Windows programs (e.g. Eclipse a

Issues encountered with new Cygwin version

2015-09-22 Thread Walter L .
Hi, I've just performed a fresh install of the latest (2.2.1) Cygwin on 64-bit Windows 7 and noticed 2 issues with the new version that I'd like to verify whether or not they are bugs: 1) The symlink to protocol file seems incorrect [user@hostname /etc]$ ls -l | grep protocol lrwxrwxrwx  1 use