Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > On Sat, Mar 14, 2009 at 10:53 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Carlos Rica <jasampler@xxxxxxxxx> writes: >> >>> 'config --replace-all ONE_ARG' was being treated as 'config NAME VALUE', >>> showing the error "key does not contain a section: --replace-all". >> >> Hmm, I am getting "error: wrong number of arguments" followed by the long >> and somewhat annoying "usage" from the parseopt table dump. > > If you find it annoying why don't you remove the usage? Because the primary target audience of the help text is not me? >> Can you work with Felipe to see if this is still needed, or needs to be >> fixed in a different way? It could be that your tests may already pass >> over there on 'next'. I didn't check. > > The new code is already checking correctly that --replace-all needs at > least two arguments. However, the "usage" is incorrect and of course > the test will come in handy. So perhaps you can pick a part of it and send in an update to your parseoptification series? I think the series is ready for 'master' sometime next week if not sooner. -- 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
