Re: parse-options does not recognize "unspecified" behavior
- From
Pranit Bauva <pranit.bauva@gmail.com>
- Date
- Mar 25, 2016, 15:03 UTC
- Message-ID
- <CAFZEwPO+iMCkMiz9ByzHm3XX7DkvSqbkpHLS+KBhyNHpE2NVJA@mail.gmail.com>
- In-Reply-To
- <20160325155805.Horde.IaS9Rdqv5fu6BmOZCj5ulLW@webmail.informatik.kit.edu>
> Deprecating doesn't mean "removing". It merely means that we add a note > to the documentation stating that the option in question is deprecated, > but we will keep supporting it for several years and releases to come.
Okay. Didn't know.
Show 5 quoted lines
> This means that '--verbose' and '--show-diff' must coexist for quite a > while, and 'git commit' should do the right thing even if both old and > new options are combined. And, of course, in combination with the new > config variable(s). I suspect that all this would be more than a half > an hour job.
Now that I think of it again, I underestimated this. It will take a lot more time and create a lot of confusion on my side.