Re: What's cooking in git.git (Jun 2018, #03; Tue, 12)

On Wed, Jun 13, 2018 at 8:56 AM Junio C Hamano wrote: > At this point, only clear fixes to regressions between v2.17.0..master > would be eligible for the final. Is the one you are pointing at a > breakage during that timeframe? No, it was introduced in v2.15.0..v2.16.0. Thanks, Stefan

Re: What's cooking in git.git (Jun 2018, #03; Tue, 12)

Stefan Beller writes: >> A tl;dr summary for -rc2 that hopefully should happen in 24 hours: >> the following four topics >> >> jk/submodule-fsck-loose-fixup >> sb/submodule-merge-in-merge-recursive >> jk/index-pack-maint >> sg/completion-zsh-workaround >> >> are planned to be merged in -rc2.

Re: What's cooking in git.git (Jun 2018, #03; Tue, 12)

> A tl;dr summary for -rc2 that hopefully should happen in 24 hours: > the following four topics > > jk/submodule-fsck-loose-fixup > sb/submodule-merge-in-merge-recursive > jk/index-pack-maint > sg/completion-zsh-workaround > > are planned to be merged in -rc2. It would be nice to have

What's cooking in git.git (Jun 2018, #03; Tue, 12)

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. A tl;dr summary for -rc2 that