Re: [PATCH v5 00/11] Untracked cache improvements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Christian Couder <christian.couder@xxxxxxxxx> writes:

> On Sat, Jan 16, 2016 at 3:57 PM, Torsten Bögershausen <tboegi@xxxxxx> wrote:
>> General question after testing UC on a slow network share:
>>
>> time ./git status
>> On branch uc-notifs63
>> Your branch is up-to-date with 'cc/uc-notifs63'.
>>
>> It took 6.27 seconds to enumerate untracked files. 'status -uno'
>> may speed it up, but you have to be careful not to forget to add
>> new files yourself (see 'git help status').
>> nothing to commit, working directory clean
>>
>> real    0m19.159s
>> user    0m0.085s
>> sys     0m0.293s
>> ----------------------
>> Does it makes sense  to hint the user about the untracked cache ?
>
> I don't think it makes sense to hint about it for now.
> When more people will have used it for a significant time perhaps.

Chicken or Egg?

I tend to think updating this message is outside of the scope of
your series, but you would not get wider adoption (hence more guinea
pigs that 'have used it for a significant time') unless you
advertise it, and I agree with Torsten that this is the message that
matters most--it is shown when we know we spent a lot of time on
what UC is meant to speed up and no other time.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]