On Wed, Jan 16, 2013 at 11:43 AM, Jeff King <peff@xxxxxxxx> wrote: > I think that is a reasonable rule that could be applied across all parts > of the namespace hierarchy. And it could be applied by the client, > because all you need to know is whether ref->old_sha1 is reachable from > ref->new_sha1. is_forwardable() did solve a UI issue. Previously all instances where old is not reachable by new were assumed to be addressable with a merge. is_forwardable() attempted to determine if the concept of forwarding made sense given the inputs. For example, if old is a blob it is useless to suggest merging it. Chris -- 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