On Wed, Jul 9, 2014 at 10:00 PM, Eric Wong normalper...@yhbt.net wrote:
Torsten Bögershausen tbo...@web.de wrote:
(And why is it 0 and not 0777)
This is to preserve the uncommon sticky/sgid/suid bits. Probably not
needed, but better to keep as much intact as possible.
Can we avoid
On Mon, Jul 14, 2014 at 6:31 AM, Erik Faye-Lund kusmab...@gmail.com wrote:
On Wed, Jul 9, 2014 at 10:00 PM, Eric Wong normalper...@yhbt.net wrote:
Torsten Bögershausen tbo...@web.de wrote:
You're saying this as if Windows is a single-user system. It's not,
but it uses ACLs rather than POSIX
Still, git might like to know what ACLs to apply to files at checkout
time. That would be a vast new feature, I think, and probably not
worth it, particularly since that would require dealing with the
different types of ACLs: NTFS/NFSv4/ZFS on the one hand, POSIX Draft
on the other, plus AFS
Am 09.07.2014 22:00, schrieb Eric Wong:
Torsten Bögershausen tbo...@web.de wrote:
(And why is it 0 and not 0777)
This is to preserve the uncommon sticky/sgid/suid bits. Probably not
needed, but better to keep as much intact as possible.
Can we avoid the fchmod() all together ?
Karsten Blees karsten.bl...@gmail.com writes:
1.) Permissions of files in .git are controlled by the core.sharedRepository
setting, and your patch seems to break that (i.e. if someone accidentally
has made .git/config world readable, git-config no longer fixes that, even
if
On 07/08/2014 10:25 PM, Ramsay Jones wrote:
On 08/07/14 20:34, Jens Lehmann wrote:
Am 07.07.2014 21:40, schrieb Torsten Bögershausen:
On 2014-07-07 19.05, Junio C Hamano wrote:
Jens Lehmann jens.lehm...@web.de writes:
Junio, do you want me to resend 02/14 without the non-portable echo -n
or
Torsten Bögershausen tbo...@web.de wrote:
(And why is it 0 and not 0777)
This is to preserve the uncommon sticky/sgid/suid bits. Probably not
needed, but better to keep as much intact as possible.
Can we avoid the fchmod() all together ?
For single-user systems, sure.
For
7 matches
Mail list logo
