Jeff King <peff@xxxxxxxx> writes: > For my workflow, it is not about "initial skip", but rather just "skip > emails that don't have patches in them at all". OK. That is different from "the subject line says 0/N so let's skip". If we can safely determine that there is no patch in a message, skipping it may feel sensible. Historically, we try to err on the safe side by stopping when we do not understand an input and that is where "Patch is empty" message came from, because skipping and continuing, even with a warning, while applying tons of patches is not good enough to get user's attention. An "ignore empty input" option (and eventually with a configuration) may not be a bad idea. -- 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