> Current state of affairs:
>
> * Enable on a per-repo basis: git update-index --untracked-cache
> * Disable on a per-repo basis: git update-index --no-cache
> * Enable system-wide: N/A
> * Disable system-wide: N/A
>
> With this patch:
>
> * Enable on a per-repo basis: git update-index
On Fri, Dec 4, 2015 at 6:54 PM, Torsten Bögershausen wrote:
>> Current state of affairs:
>>
>> * Enable on a per-repo basis: git update-index --untracked-cache
>> * Disable on a per-repo basis: git update-index --no-cache
>> * Enable system-wide: N/A
>> * Disable system-wide:
On Thu, Dec 3, 2015 at 5:10 PM, Torsten Bögershausen wrote:
> [snip all good stuff]
>
> First of all:
> Thanks for explaining it so well
>
> I now can see the point in having this patch.
> (Do the commit messages reflect all this ? I need to re-read)
Maybe not. I will have a look
[snip all good stuff]
First of all:
Thanks for explaining it so well
I now can see the point in having this patch.
(Do the commit messages reflect all this ? I need to re-read)
The other question is: Do you have patch on a public repo ?
And, of course, can we add 1 or 2 test cases ?
Thanks
On Wed, Dec 2, 2015 at 8:12 AM, Torsten Bögershausen wrote:
> On 12/01/2015 09:31 PM, Christian Couder wrote:
>>
>> When we know that mtime is fully supported by the environment, we
>> might want the untracked cache to be always used by default without
>> any mtime test or kernel
When we know that mtime is fully supported by the environment, we
might want the untracked cache to be always used by default without
any mtime test or kernel version check being performed.
Also when we know that mtime is not supported by the environment,
for example because the repo is shared
On 12/01/2015 09:31 PM, Christian Couder wrote:
When we know that mtime is fully supported by the environment, we
might want the untracked cache to be always used by default without
any mtime test or kernel version check being performed.
I'm not sure if ever "we know" ?
How can we know without
7 matches
Mail list logo