On Nov 27, 2007, at 5:19 PM, Junio C Hamano wrote:
How does this interact with the "pretend to have fetched back immediately" supported by modern git-push?
That continues to fire, but it updates the local tracking ref to point to the SHA1 that was pushed, which isn't the actual remote ref. So you have to do a real fetch to get the local tracking ref pointed to the right place. In other words, that feature doesn't do any good in this context, but it doesn't really hurt anything either.
It would of course be better if git-push could notice that it needs to do an actual fetch. I think it'd be sufficient to transmit the final remote ref SHA1 back to git-push, and if it doesn't match what was pushed, that's a sign that a fetch is needed. But that change wouldn't be mutually exclusive with this patch, I believe.
-Steve - 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
