>>> If I leave off the noacl and do a clone followed by a push and pull
>>> we
>>> >end up with the following error in the Windows security tab:
>>> > The permissions on file.cpp are incorrectly ordered, which may
>>> >cause some entries to be ineffective.
>> Yes, I've seen that before; it's a pr
>To be absolutely clear: if you mount an NFS share with noacl set, you get a
>noticable speed increase versus not setting noacl?
Let me clear this up a bit. The group is working on local
repositories that happen to exist on local NTFS drives under Windows.
These drives are the same local drives t
On 5/14/2016 8:03 AM, Adam Dinwoodie wrote:
If I leave off the noacl and do a clone followed by a push and pull we
>end up with the following error in the Windows security tab:
> The permissions on file.cpp are incorrectly ordered, which may cause
>some entries to be ineffective.
Yes, I've see
On Tue, May 10, 2016 at 09:59:50AM -0400, andrew stern wrote:
> >I'm not sure I understand what you're seeing: if your repository is
> >already set up with core.filemode set to false, Git won't check the
> >executable flag on the files. What leads you to think the speed
> >slow-down is related to
>I'm not sure I understand what you're seeing: if your repository is already
>set up with core.filemode set to false, Git won't check the executable flag on
>the files. What leads you to think the speed slow-down is related to
>>checking whether the file is executable?
>If setting cygexec make
On Tue, May 10, 2016 at 09:15:48AM -0400, andrew stern wrote:
> >I suspect this isn't a problem with the Git upgrade but with recent
> >changes that have been being made to how the core Cygwin dll handles
> >permissions.
>
> >That being said, can you try running `git config core.filemode false` in
>I suspect this isn't a problem with the Git upgrade but with recent
>changes that have been being made to how the core Cygwin dll handles
>permissions.
>That being said, can you try running `git config core.filemode false` in
>the repository, re-enabling noacl, and see if that has things running
On Mon, May 09, 2016 at 03:59:39PM -0400, andrew stern wrote:
> If I change my fstab back so that it does not include the noacl option
> on the line the merge is much faster:
>
> 15:51:22.288607 git.c:350 trace: built-in: git 'merge'
> 'FETCH_HEAD' Updating 154cf50..a0f35eb
> Fast-fo
If I change my fstab back so that it does not include the noacl option
on the line the merge is much faster:
15:51:22.288607 git.c:350 trace: built-in: git 'merge'
'FETCH_HEAD' Updating 154cf50..a0f35eb
Fast-forward
15:55:18.347594 run-command.c:336 trace: run_command: 'gc' '--
9 matches
Mail list logo
