24.06.2019, 13:05, "Junio C Hamano" <gitster@xxxxxxxxx>: > Andrey <ahippo@xxxxxxxxx> writes: > >> 20.06.2019, 00:35, "Junio C Hamano" <gitster@xxxxxxxxx>: >>> * am/p4-branches-excludes (2019-04-02) 8 commits >>> - git-p4: respect excluded paths when detecting branches >>> - git-p4: add failing test for "git-p4: respect excluded paths when detecting branches" >>> - git-p4: don't exclude other files with same prefix >>> - git-p4: add failing test for "don't exclude other files with same prefix" >>> - git-p4: don't groom exclude path list on every commit >>> - git-p4: match branches case insensitively if configured >>> - git-p4: add failing test for "git-p4: match branches case insensitively if configured" >>> - git-p4: detect/prevent infinite loop in gitCommitByP4Change() >>> >>> "git p4" update. >>> >>> Is this ready for 'next'? >> >> Junio, >> >> I haven't got any new feedback on the patch series in the past 2.5 months. >> From my point of view, these are ready for next. > > Thanks. When I ask "Is this ready", I am asking for opinion(s) from > third-party, not self nomination ;-) Ah, ok, sorry. :) I just haven't seen any related comments to any of your previous "What's cooking" emails, so thought I should send a keepalive email just in case. > Let's merge it down to 'next' and to 'master' anyway. Thank you! That'll be great! -- Andrey.
