mhagger@xxxxxxxxxxxx writes: > This patch can be squashed on top of "is_refname_available(): query > only possibly-conflicting references", or applied at the end of > mh/ref-api-take-2; it does not conflict with the two commits later in > the series. Thanks. At the microscopic level (i.e. in the context of the said series), the patch makes sense to me. However, I'd rather see us spend effort to make absolutely sure that other topics already in next that touch the related codepaths (I think you have two such series yourself and I suspect there are other minor fixes that may textually conflict) are in good shape and have them graduate early after 1.7.8 ships, before queuing a re-roll of the ref-api series, which is rather extensive. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html