Re: [PATCH v2 0/4] Deprecate "not allow as-is commit with i-t-a entries"

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 7, 2012, 16:41 UTC
Message-ID: <7v8vke38a1.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1328618804-31796-1-git-send-email-pclouds@gmail.com>

Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:

Show 12 quoted lines

>  - git-add.txt changes are removed. In the end all kinds of commit
>    behave the same way, not worth putting more explanation during the
>    transition.
>
>  - reword config text and warning text (or more precisely copy/paste
>    from Junio/Jonathan's words)
>
>  - Hard coded release numbers are removed. Now it's simply "in future".
>
>  - Step 2 may be too annoying. Users are warned on every commit if
>    commit.ignoreIntentToAdd is set. I think it's good because it keeps
>    config file clean, but people may think otherwise.

Ahh, thanks.

But when I said "let's admit that this is just fixing an UI mistake, no configuration, no options", I really meant it. Without the backward compatiblity "For now please do not fix this bug for me and keep being buggy until I get used to the non-buggy behaviour" fuss, which we never do to any bugfix.

That is how we are planning to handle "git merge" update to spawn editor in interactive session in the next release. There is no "Please keep the buggy behaviour" option; only an environment variable to help when we mistake a scripted use as interactive, whose support is not going away because it is not about "until I get used to the new behaviour".