From: Pranit Bauva <pranit.bauva@gmail.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Jeff King <peff@peff.net>, Stefan Beller <sbeller@google.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Git List <git@vger.kernel.org>
Subject: Re: parse-options does not recognize "unspecified" behavior
Date: Fri, 25 Mar 2016 20:33:06 +0530 [thread overview]
Message-ID: <CAFZEwPO+iMCkMiz9ByzHm3XX7DkvSqbkpHLS+KBhyNHpE2NVJA@mail.gmail.com> (raw)
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.
> 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.
next prev parent reply other threads:[~2016-03-25 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 19:51 parse-options does not recognize "unspecified" behavior Pranit Bauva
2016-03-16 20:49 ` Jeff King
2016-03-16 21:06 ` Pranit Bauva
2016-03-16 21:23 ` Jeff King
2016-03-16 21:37 ` Eric Sunshine
2016-03-16 21:41 ` Pranit Bauva
2016-03-16 21:44 ` Jeff King
2016-03-16 21:53 ` Stefan Beller
2016-03-16 23:16 ` Jeff King
2016-03-16 23:33 ` Stefan Beller
2016-03-17 1:43 ` Jeff King
2016-03-17 5:32 ` Eric Sunshine
2016-03-17 5:40 ` Jeff King
2016-03-19 11:25 ` SZEDER Gábor
2016-03-19 16:55 ` Pranit Bauva
2016-03-25 14:58 ` SZEDER Gábor
2016-03-25 15:03 ` Pranit Bauva [this message]
2016-03-16 21:37 ` Pranit Bauva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFZEwPO+iMCkMiz9ByzHm3XX7DkvSqbkpHLS+KBhyNHpE2NVJA@mail.gmail.com \
--to=pranit.bauva@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.com \
--cc=szeder@ira.uka.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).