On Mon, Jul 25, 2016 at 6:04 PM, Duy Nguyen wrote:
>
> Hmm.. can you do the counting separately? A shared cache_entry must
> have its field "index" greater than zero. By counting the number of
> entries whose index is zero (i.e. not shared) against the total number
> of real (*) entries, you shoul
On Sat, Jul 23, 2016 at 6:11 PM, Christian Couder
wrote:
> Ok, I started working on automatically pushing back all changes to the
> shared index when the percentage of entries in linked vs shared
> indexes is greater than 25% (maybe I will make it configurable later).
> It is very basic and doesn'
On Tue, Jul 12, 2016 at 6:01 PM, Duy Nguyen wrote:
> On Mon, Jul 11, 2016 at 7:22 PM, Christian Couder
> wrote:
>> Future work
>> ~~~
>>
>> One thing that is probably missing is a mechanism to avoid having too
>> many changes accumulating in the (split) index while in split index
>> mode.
On Mon, Jul 11, 2016 at 7:22 PM, Christian Couder
wrote:
> Future work
> ~~~
>
> One thing that is probably missing is a mechanism to avoid having too
> many changes accumulating in the (split) index while in split index
> mode. The git-update-index documentation says:
>
> If split
Goal
We want to make it possible to use the split-index feature
automatically by just setting a new "core.splitIndex" configuration
variable to true.
This can be valuable as split-index can help significantly speed up
`git rebase` especially along with the current work to libify `git
apply`.
5 matches
Mail list logo
