Pierre Habouzit <madcoder@xxxxxxxxxx> writes: > Yep, let's do it then. Note that's the reason why I felt we need a > manual page about this, because we should give some guidelines of what > is safe for scripting. There are some fallouts from the series, though. I've fixed up git-tag but I strongly suspect all of parseopt users now need careful auditing. If we cannot be confident with the parseoptified commands within reasonably short timeframe by -rc1, we may end up having to revert the parseopt changes from them, which I'd rather avoid, but if you look at the git-tag change (especially for -l) you would understand it. The "must stick" restriction feels Ok on paper but in practice it looks rather draconian and very user unfriendly. I'll be sending out two patches shortly. The result will sit in 'pu' waiting for an Ack and/or improvement, but that will happen only when I got around pushing things out, which may come later than you see the patches. - 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
