Emily Xie <emilyxxie@xxxxxxxxx> writes: > The fix for this issue requires a two-step approach. As > there may be existing scripts that knowingly use empty > strings in this manner, the first step simply invokes a > warning that (1) declares using empty strings to > match all paths will become invalid and (2) asks the user > to use "." if their intent was to match all. > > For step two, a follow-up patch several release cycles > later will remove the warnings and throw an error instead. > > This patch is the first step. > > Signed-off-by: Emily Xie <emilyxxie@xxxxxxxxx> > Reported-by: David Turner <novalis@xxxxxxxxxxx> > Mentored-by: Michail Denchev <mdenchev@xxxxxxxxx> > Thanks-to: Sarah Sharp <sarah@xxxxxxxxxxxx> and James Sharp <jamey@xxxxxxxxxxx> > --- Looks sensible. I personally do not think warn-only-once matters in practice, but now you have implemented it, it is an additional nice touch ;-) Will queue. Thanks. -- 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