Jeff King <p...@peff.net> writes: > We can't fully process the refspecs until we have talked to the other > side, because they may involve matching refs from the remote; I don't > think git even really looks at them until after we've connected. > > But I think there are some obvious cases, like a bogus left-hand side > (i.e., what you have here) that cannot ever succeed, no matter what the > other side has. We could sanity check the refspecs before doing anything > else.
The user's wallclock time is more important than machine cycles, checking things we could check before having the user do things is a good principle to follow. I wish that the solution did not have to involve doing the same computation twice, but I do not think there is a clean way around that in this codepath. Thanks. -- 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
