Quoting Junio C Hamano <gitster@xxxxxxxxx>: > I wrote that side note after googling around and found that many users > outside git community wondering what a strange way to announce a new > feature it was, and I think they are right. I stupidly said that we > should tone the message neutral, because we might want to change the > default in the future but we are still not committed. But the end result > is just a confusing advertisement of an optional feature. > > I actually think that the right course of action at this point is this > patch instead. We keep the default, we do not annoy the users, and people > who want to use a non-default configuration can use the feature. An alternative approach could be to rewrite the message to say that we will change the default to something other than 'matching' as the first step, and then apply Finn Arne's patch as the second step to really force people to choose, because I thought the plan was to switch the default to something other than the matching. But apparently I misremembered. I googled and found nobody explaining that this message is a preparatory step for such transition. The only reactions I found were the ones that said this is a strange way to advertize a new feature. I think you are correct, and I think your patch is the right way forward. -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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