Lars Schneider <larsxschnei...@gmail.com> writes: >> On 17 Jun 2016, at 05:20, Junio C Hamano <gits...@pobox.com> wrote: >> >> ... >> >> * mh/split-under-lock (2016-05-13) 33 commits >> (merged to 'next' on 2016-06-03 at 2e71330) >> + lock_ref_sha1_basic(): only handle REF_NODEREF mode >> + ... >> + t1404: demonstrate a bug resolving references >> (this branch is used by mh/ref-iterators, mh/ref-store and >> mh/update-ref-errors.) >> >> Further preparatory work on the refs API before the pluggable >> backend series can land. >> >> Will merge to 'master'. > > This topic seems break two git-p4 tests (t9801 and t9803) on next: > https://travis-ci.org/git/git/jobs/137333785 > > According to git bisect the commit "ref_transaction_update(): > check refname_is_safe() at a minimum" (3da1f3) introduces the problem: > https://s3.amazonaws.com/archive.travis-ci.org/jobs/138457628/log.txt > (scroll all the way down to see the bisecting)
Thanks. Let's hold it and all of its dependents to see what is going on. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
