Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)
- From
Ben Peart <peartben@gmail.com>
- Date
- Apr 16, 2019, 15:27 UTC
- Message-ID
- <a65a261d-a8dd-7610-bcaf-47071df1d659@gmail.com>
- In-Reply-To
- <xmqqef62ozny.fsf@gitster-ct.c.googlers.com>
On 4/16/2019 9:19 AM, Junio C Hamano wrote:
Show 15 quoted lines
> Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration branches, but I am still holding onto them. > > Yet another batch of ~30 topics have graduated to 'master', and > 'next' has also gained ~25 topics. We may want to start merging > down fixes to 'maint' for a 2.21.1. > > You can find the changes described here in the integration branches > of the repositories listed at > > http://git-blame.blogspot.com/p/git-public-repositories.html > > --------------------------------------------------
<snip>
Show 13 quoted lines
> * 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? I'm unaware of any requests for a re-roll. If something is needed, please let me know.