On Tue, Oct 11, 2011 at 04:50:46PM -0700, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > It looks like we also use it in remote.c:count_refspec_match, but I > > haven't figured out if that can trigger a warning or not. > > It starts sounding like that the ill-thought-out warning should be ripped > out regardless of what other things we do. Maybe. I think it is not the warning that is wrong, but that it is exposing a slightly hack-ish part of git (that we consider things like $GIT_DIR/config as possible refs, and just silently reject them because they happen not to have the right format). On the other hand, it has been working fine that way for years, so maybe it is not worth changing now. At any rate, I think the changes should be all or nothing. If the warning goes away, fine. But if the warning stays, and dwim_ref is going to have special rules for looking in the top-level $GIT_DIR, then things like shorten_unambiguous_ref need to respect those rules, or we've just created a new bug. -Peff -- 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