On Wed, Jan 16, 2013 at 10:48 AM, Junio C Hamano <gits...@pobox.com> wrote: > It is fine when pushing into "refs/tags/" hierarchy. It is *NOT* > OK if the type check does not satisfy this function. In that case, > we do not actually see the existence of the destination as a > problem, but it is reported as such. We are blocking because we do > not like the type of the new object or the type of the old object. > If the destination points at a commit, the push can succeed if the > user changes what object to push, so saying "you cannot push because > the destination already exists" is just wrong in such a case.
So the solution is to revert back to recommending a merge? -- 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
