Ben Peart <peartben@xxxxxxxxx> writes: >> * bp/post-index-change-hook (2019-02-15) 1 commit >> (merged to 'next' on 2019-03-11 at cb96d1d7c4) >> + read-cache: add post-index-change hook >> >> Originally merged to 'next' on 2019-02-23 >> >> A new hook "post-index-change" is called when the on-disk index >> file changes, which can help e.g. a virtualized working tree >> implementation. >> >> Will cook in 'next'. > > Anything in particular this is waiting for? The second user, other than the originating party, who jumps up and down asking for it to be in the upcoming release, preferrably with their own use case to reenforce the justification why it is a good idea to have the hook. That is what I've been hoping to see, so that I can point fingers at you and that second person when it turns out that the hook was a bad idea for whatever reason ;-) Not that any feature must have support from multiple parties. It was just that waiting for the second one was the easiest way to gauge the interest.
